DOCSLIB.ORG

Using Domain-Specific Languages for Event-Based

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Using Domain-Specific Languages for Event-Based Die approbierte Originalversion dieser Diplom-/Masterarbeit ist an der Hauptbibliothek der Technischen Universität Wien aufgestellt (http://www.ub.tuwien.ac.at). The approved original version of this diploma or master thesis is available at the main library of the Vienna University of Technology (http://www.ub.tuwien.ac.at/englweb/). Using Domain-Specific Languages for Event-Based QoS Monitoring in Service-Oriented Environments DIPLOMARBEIT zur Erlangung des akademischen Grades Diplom-Ingenieur im Rahmen des Studiums Software Engineering & Internet Computing eingereicht von Matthias Irlacher Matrikelnummer 0225106 an der Fakultät für Informatik der Technischen Universität Wien Betreuung: Univ.-Prof. Dr. Schahram Dustdar Mitwirkung: Dipl.-Ing. Dr.techn. Ernst Oberortner Mag.rer.soc.oec. Philipp Leitner Wien, 15.11.2011 (Unterschrift Verfasser) (Unterschrift Betreuung) Technische Universität Wien A-1040 Wien Karlsplatz 13 Tel. +43-1-58801-0 www.tuwien.ac.at Erklärung zur Verfassung der Arbeit Matthias Irlacher Rustengasse 8/12, 1150 Wien Hiermit erkläre ich, dass ich diese Arbeit selbständig verfasst habe, dass ich die verwende- ten Quellen und Hilfsmittel vollständig angegeben habe und dass ich die Stellen der Arbeit - einschließlich Tabellen, Karten und Abbildungen -, die anderen Werken oder dem Internet im Wortlaut oder dem Sinn nach entnommen sind, auf jeden Fall unter Angabe der Quelle als Ent- lehnung kenntlich gemacht habe. (Ort, Datum) (Unterschrift Verfasser) i Abstract As the paradigm of Services-Oriented Architecture (SOA) gets more widespread, the quality of the used services also gets more important. Not only is this Quality of Service (QoS) important to human users, but to other services. Monitoring and automatic checks for violations of Services Level Agreements (SLAs) are a necessary and interesting topic. This thesis demonstrates and evaluates a system for the measuring of service quality using a centralized monitor and a minimal-invasive framework at the clients and services. It uses three domain-specific languages (DSLs) to describe SLAs (SLADSL), define measuring points and their context (MPDSL) and create metrics based on the defined measuring points (MDDSL). In addition to the languages, a system for distribution the measuring point information is proposed. The concrete measurement takes place at the clients and services and the measured raw data is sent to the monitor. The monitor uses transformations, generated from MDDSL statements, to calculate metrics from the raw events in a Complex Event Processing (CEP) system. The goal of this thesis was to find a fast, event-based approach to define and measure QoS prop- erties, based on an existing approach by Ernst Oberortner. It had to be expressive, extensible and at the same time try to keep the influence and dependence on the measured systems as small as possible. Amongst other things, this should be achieved by using a separation of SLA, met- ric descriptions and measuring point definitions and the possibility to change SLAs and metric descriptions at runtime. The evaluation of the approach shows a minimal influence at the mea- surement locations when using interceptor-based measurement. The central monitor proves to be a bottleneck, but a possible solution is proposed by splitting the monitor into multiple sys- tems. The concept of separate MPDSL and MDDSL allows to define a variety of QoS properties and enables great extensibility, even including other measurement systems. An evaluation tests the prototype and discusses some further improvements of the system. iii Kurzfassung Da das Paradigma der Services-Oriented Architecture (SOA) sich immer weiter verbreitet, wird auch die Qualität der benutzen Services immer wichtiger. Diese Quality of Service (QoS) ist dabei nicht nur wichtig für menschliche Nutzer, sondern auch für andere Services. Das Über- wachen und automatische Überprüfen auf Verletzungen von Services Level Agreements (SLAs) sind ein notwendiges und interessantes Thema. Diese Diplomarbeit demonstriert und evaluiert ein System, welches Servicequalität mittels eines zentralen Monitors und eines minimal-invasiven Frameworks bei Clients und Services misst. Sie verwendet drei domain-specific languages (DSLs) um SLAs zu beschreiben (SLADSL), Mess- punkte und ihren Kontext zu definieren (MPDSL) und Metriken, basierend auf den definierten Messpunkten, zu erstellen (MDDSL). Zusätzlich wird ein System zum Verteilen der Messpunkt- Informationen vorgeschlagen. Das konkrete Messen findet bei Clients und Services statt, die gemessenen Rohdaten werden daraufhin an den Monitor gesendet. Der Monitor benutzt Trans- formationen, die aus MDDSL Beschreibungen generiert wurden, um in einem Complex Event Processing (CEP)-System Metriken aus den Rohdaten zu generieren. Das Ziel dieser Diplomarbeit war es, einen schnellen, event-basierten Ansatz zu finden, um QoS Properties zu definieren und zu messen, basierend auf einem Ansatz von Ernst Oberortner. Er musste ausdrucksstark und erweiterbar sein und gleichzeitig versuchen den Einfluss auf und die Abhängigkeit von dem gemessenen System so klein wie möglich zu halten. Unter anderem soll- te dies durch eine Trennung von SLA, Metrikbeschreibung und Messpunktdefinitionen, sowie durch die Möglichkeit SLAs und Metrikbeschreibungen zur Laufzeit zu ändern, erreicht werden. Die Evaluierung dieses Ansatzes zeigt einen minimalen Einfluss am Messort bei Benutzung ei- ner Interceptor-basierenden Messung. Der zentrale Monitor erweist sich als Flaschenhals, doch eine mögliche Lösung, durch Auftrennen des Monitors in mehrere Systeme, wird vorgeschlagen. Das Konzept der getrennten MPDSL und MDDSL erlaubt uns eine Vielfalt von QoS Eigenschaf- ten zu definieren und ermöglicht gute Erweiterbarkeit, sogar durch das Miteinbeziehen anderer Messsysteme. Eine Evaluierung testet den Prototypen und diskutiert weitere Verbesserungen des Systems. v Contents 1 Introduction 1 1.1 Motivation . 1 1.2 Problem Statement . 3 1.3 Contribution . 3 1.4 Organization . 5 2 State of the Art 7 2.1 Service-Oriented Architectures . 7 2.1.1 Services . 7 2.1.2 The Basic Service-Oriented Architecture . 8 2.1.3 Service Composition . 9 2.1.4 Benefits . 10 2.2 Web Services . 10 2.2.1 SOAP 1.1 . 11 2.2.2 WSDL 1.1 . 12 2.2.3 Discovery . 13 2.3 Quality of Service . 14 2.3.1 Metrics . 14 2.3.2 Service Level Agreements . 15 2.3.3 Measurement . 15 2.4 Complex Event Processing . 16 2.4.1 Events . 17 2.4.2 Concepts . 18 2.5 Domain-Specific Languages . 20 2.5.1 Generic Structure . 21 2.5.2 Patterns . 21 2.5.3 Advantages and Disadvantages . 23 3 Related Work 25 3.1 Monitoring . 25 3.1.1 Quality of Service Levels . 27 3.1.2 QoS Management . 28 3.2 Extended QoS Metrics . 30 3.2.1 Semantic Approaches . 32 3.2.2 Temporal QoS Parameter Evaluation . 34 3.2.3 Monitoring Compositions . 35 vii 4 Background 39 4.1 Apache CXF . 39 4.1.1 Message Processing . 39 4.1.2 Building Web Services using CXF . 40 4.2 Esper . 42 4.2.1 Event Processing Concepts . 42 4.2.2 Performance . 44 4.3 Frag . 45 4.3.1 Core Language . 45 4.3.2 Using Domain-Specific Languages . 46 4.3.3 Embedding into Java . 46 4.4 QuaLa . 47 4.4.1 Architecture . 48 4.4.2 The Domain-Specific Languages . 48 4.4.3 Supported Measurements . 49 5 Design 51 5.1 Motivating Example . 51 5.2 Architecture . 53 5.2.1 Measuring Location Framework . 55 5.2.2 Monitor . 56 5.3 DSLs . 58 5.3.1 MPDSL . 58 5.3.2 SLADSL . 59 5.3.3 MDDSL . 63 6 Implementation 79 6.1 Components . 79 6.1.1 Monitor . 79 6.1.2 Measuring Location Framework . 82 6.1.3 Web Interface . 85 6.2 DSL Transformation . 87 6.2.1 SLADSL . 88 6.2.2 MDDSL . 88 7 Evaluation 91 7.1 Quantitative Evaluation . 91 7.1.1 Setup . 91 7.1.2 Performance of the MLF . 93 7.1.3 Performance of the Monitor . 95 7.2 Qualitative Evaluation, Open Problems and Limitations . 97 7.2.1 Platform Impact . 97 7.2.2 Performance Impact . 97 7.2.3 Expressiveness of the DSLs . 100 viii 7.2.4 Security and Trust . 104 7.2.5 Areas of Application . 105 8 Conclusion and Future Work 107 8.1 Future Work . 108 A List of Abbreviations 109 B Listings 113 B.1 Used Metrics . 113 B.1.1 Standard Metrics . 113 B.1.2 Application-Specific Metrics . 120 B.2 Used SLA . 121 B.3 Used MP Definitions . 121 B.3.1 RMP . 121 B.3.2 AMP . 122 B.3.3 PMP . 122 B.4 Other listings . ..
Load more

Recommended publications
  • A Survey of Architectural Styles.V4
    Survey of Architectural Styles Alexander Bird, Bianca Esguerra, Jack Li Liu, Vergil Marana, Jack Kha Nguyen, Neil Oluwagbeminiyi Okikiolu, Navid Pourmantaz Department of Software Engineering University of Calgary Calgary, Canada Abstract— In software engineering, an architectural style is a and implementation; the capabilities and experience of highest-level description of an accepted solution to a common developers; and the infrastructure and organizational software problem. This paper describes and compares a selection constraints [30]. These styles are not presented as out-of-the- of nine accepted architectural styles selected by the authors and box solutions, but rather a framework within which a specific applicable in various domains. Each pattern is presented in a software design may be made. If one were to say “that cannot general sense and with a domain example, and then evaluated in be called a layered architecture because the such and such a terms of benefits and drawbacks. Then, the styles are compared layer must communicate with an object other than the layer in a condensed table of advantages and disadvantages which is above and below it” then one would have missed the point of useful both as a summary of the architectural styles as well as a architectural styles and design patterns. They are not intended tool for selecting a style to apply to a particular project. The to be definitive and final, but rather suggestive and a starting paper is written to accomplish the following purposes: (1) to give readers a general sense of several architectural styles and when point, not to be used as a rule book but rather a source of and when not to apply them, (2) to facilitate software system inspiration.
    [Show full text]
  • Diplomarbeit Im Fachbereich Elektrotechnik & Informatik an Der
    Bachelor Thesis Prannoy Mulmi Design and Implementation of an Archive Microservice solution for the Multi-Agent Research and Simulation Distributed System Fakultät Technik und Informatik Faculty of Engineering and Computer Science Department Informations- und Department of Information and Elektrotechnik Electrical Engineering Prannoy Mulmi Design and Implementation of an Archive Microservice solution for the Multi-Agent Research and Simulation Distributed System Bachelor Thesis based on the study regulations for the Bachelor of Engineering degree programme Information Engineering at the Department of Information and Electrical Engineering of the Faculty of Engineering and Computer Science of the Hamburg University of Applied Sciences Supervising examiner : Prof. Dr. rer. nat. Henning Dierks Second Examiner : Prof. Dr. rer. nat. Thomas Clemen Day of delivery 23. Juli 2018 Prannoy Mulmi Title of the Bachelor Thesis Design and Implementation of an Archive Microservice solution for the Multi-Agent Research and Simulation Distributed System Keywords Distributed System, Microservice, Two-Phase commit protocol, Archive, Decentrali- zed data, Multi-Agent Research and Simulation (MARS) Abstract This thesis introduces the design and implementation of an Archive Microservice in the Multi-Agent Research and Simulation (MARS) framework. Due to the distributed architecture of the system, the process of the archive and restore is complex to imple- ment and maintain as there multiple possibilities of failure. This thesis uses different strategies to
    [Show full text]
  • Methods & Tools
    METHODS & TOOLS Practical knowledge for the software developer, tester and project manager ISSN 1661-402X Spring 2011 (Volume 19 - number 1) www.methodsandtools.com The Salesmen/Developers Ratio at Software Vendors Many of us might think that software is a technological industry. Maybe. But maybe not. If you consider Oracle or Microsoft, I suppose that few of us would consider them as technology leaders, but we will all recognize their financial strength and marketing power. Long lasting organizations in the software industry might have more financial strength than technological capabilities. The recent conflict between Oracle and the creator of Hudson, an open source continuous integration server, is just another episode in the opposition between developers- and salesmen-driven software companies. On one side you have Oracle, for which Hudson is just small project inherited from the Sun buyout and that owns the "Hudson" brand. On the other side, you find Kohsuke Kawaguchi, who created Hudson and wants keep some control on its development. Hudson has been "forked", the open source code being used to start another project. You now have a Jenkins CI project that includes most of the active Hudson contributors and a Hudson CI project backed by Oracle and Sonatype, the commercial company behind the Maven project. Everything is however not black and white. Kohsuke Kawaguchi has joined Cloudbees, a company that has some management and financing coming from ex-JBoss managers, people that know how to make money with open source software. These people are not working hard for the only sake of technology evolution. You can judge the main orientation of a company looking at its salesmen/developers ratios.
    [Show full text]
  • Mutable Class Design Pattern Nikolay Malitsky Nova Southeastern University, [email protected]
    Nova Southeastern University NSUWorks CEC Theses and Dissertations College of Engineering and Computing 2016 Mutable Class Design Pattern Nikolay Malitsky Nova Southeastern University, [email protected] This document is a product of extensive research conducted at the Nova Southeastern University College of Engineering and Computing. For more information on research and degree programs at the NSU College of Engineering and Computing, please click here. Follow this and additional works at: https://nsuworks.nova.edu/gscis_etd Part of the Other Computer Sciences Commons, and the Theory and Algorithms Commons Share Feedback About This Item NSUWorks Citation Nikolay Malitsky. 2016. Mutable Class Design Pattern. Doctoral dissertation. Nova Southeastern University. Retrieved from NSUWorks, College of Engineering and Computing. (956) https://nsuworks.nova.edu/gscis_etd/956. This Dissertation is brought to you by the College of Engineering and Computing at NSUWorks. It has been accepted for inclusion in CEC Theses and Dissertations by an authorized administrator of NSUWorks. For more information, please contact [email protected]. Mutable Class Design Pattern by Nikolay Malitsky A dissertation submitted in partial fulfillment of the requirements for the degree of Doctor of Philosophy in Computer Science Graduate School of Computer and Information Sciences Nova Southeastern University 2016 We hereby certify that this dissertation, submitted by Nikolay Malitsky, conforms to acceptable standards and is fully adequate in scope and quality to fulfill the dissertation requirements for the degree of Doctor of Philosophy. _____________________________________________ ________________ Michael J. Laszlo, Ph.D. Date Chairperson of Dissertation Committee _____________________________________________ ________________ Francisco J. Mitropoulos, Ph.D. Date Dissertation Committee Member _____________________________________________ ________________ Amon B.
    [Show full text]
  • Security Pattern Validation and Recognition
    Security-Pattern Recognition and Validation Dissertation Submitted by Michaela Bunke on 12th December 2018 to the Universit¨atBremen Faculty of Mathematics and Computer Science in partial fulfillment of the requirements for the degree of Doktor der Ingenieurwissenschaften { Dr.-Ing. { Reviewed by Prof. Dr. Hans-J¨orgKreowski Universit¨atBremen, Germany and Dr. Karsten Sohr Universit¨atBremen, Germany In Memorial of Ilse Schlamilch Karl Schlamilch Manfred Friedrichs 21 November 1924 03 March 1927 29 August 1935 09 June 2017 19 June 2018 3 July 2017 ABSTRACT The increasing and diverse number of technologies that are connected to the Internet, such as distributed enterprise systems or small electronic devices like smartphones, brings the topic IT security to the foreground. We interact daily with these technologies and spend much trust on a well-established software development process. However, security vulnerabilities appear in software on all kinds of PC(- like) platforms, and more and more vulnerabilities are published, which compromise systems and their users. Thus, software has also to be modified due to changing requirements, bugs, and security flaws and software engineers must more and more face security issues during the software design; especially maintenance programmers must deal with such use cases after a software has been released. In the domain of software development, design patterns have been proposed as the best-known solutions for recurring problems in software design. Analogously, security patterns are best practices aiming at ensuring security. This thesis develops a deeper understanding of the nature of security patterns. It focuses on their validation and detection regarding the support of reviews and maintenance activities.
    [Show full text]
  • A CASE STUDY by Siegfried Steiner ([email protected])
    BIG DATA PROCESSING THE LEAN WAY – A CASE STUDY by Siegfried Steiner ([email protected]) 19/08/14 – 17/01/21 2 Content 1.Preface.............................................................................................................3 2.Abstract...........................................................................................................3 3.The mission.....................................................................................................4 4.Terminology.....................................................................................................5 5.Constraints......................................................................................................6 6.Approach.........................................................................................................7 7.Technology stack.............................................................................................8 8.Development process....................................................................................10 Excursus: Scrum.....................................................................................10 Excursus: Test-driven development........................................................11 9.Into the cloud: Scalability..............................................................................12 Excursus: IPO Model...............................................................................13 1.Input - Receive requests (and process output)..........................................14 Excursus: Front
    [Show full text]
  • Architectural Styles and Patterns
    Architectural Styles and Patterns Wednesday 13 February 13 Architectural Patterns & Styles Consensus Controversy • Established • Philosophy (context- Solutions problem-solution vs components- Common • connections) vocabulary Granularity (vs Document • • Design patterns) Reason over quality • • Categorization Wednesday 13 February 13 Architectural Patterns (Wikipedia) • Presentation- abstraction- • Peer-to-peer control • Service-oriented • Three-tier architecture • Pipeline • Naked Objects Implicit Invocation • Model-View • Controller • Blackboard Wednesday 13 February 13 Architectural Patterns (Shaw & Garland) • Dataflow Systems -- Batch, Pipes and Filters • Call-and-return systems -- Main program and subroutines, OO systems, Hierarchical Layers • Independent components -- Communicating processes, Event systems • Virtual Machines -- Interpreters, Rule-based systems • Data-Centered Systems -- Databases, Hypertext systems Blackboards Wednesday 13 February 13 Elements of Architecture (Shaw & Garland) Components Connectors • Clients • Procedure calls • Servers • Events broadcast • Filters • Database protocols • Layers • Pipes • Databases - What are the structural patterns permitted? - What is the underlying computational model? - What are the invariants of the style? BUT ... - What are examples of its use? - What are the tradeoffs? - ... Wednesday 13 February 13 Architectural Patterns (Baas, Clements & Kazman) • Dataflow Systems -- Batch, Pipes and Filters • Data-Centered -- Repository, Blackboard • Virtual machine -- Interpreter, Rule-based
    [Show full text]
  • Microservices Antipatterns and Pitfalls
    Microservices AntiPatterns and Pitfalls Mark Richards Beijing Boston Farnham Sebastopol Tokyo Microservices Antipatterns and Pitfalls by Mark Richards Copyright © 2016 O’Reilly Media, Inc. All rights reserved. Printed in the United States of America. Published by O’Reilly Media, Inc., 1005 Gravenstein Highway North, Sebastopol, CA 95472. O’Reilly books may be purchased for educational, business, or sales promotional use. Online editions are also available for most titles (http://safaribooksonline.com). For more information, contact our corporate/institutional sales department: 800-998-9938 or [email protected]. Editor: Brian Foster Interior Designer: David Futato Production Editor: Melanie Yarbrough Cover Designer: Karen Montgomery Copyeditor: Christina Edwards Illustrator: Rebecca Demarest Proofreader: Amanda Kersey July 2016: First Edition Revision History for the First Edition 2016-07-06: First Release The O’Reilly logo is a registered trademark of O’Reilly Media, Inc. Microservices AntiPatterns and Pitfalls, the cover image, and related trade dress are trademarks of O’Reilly Media, Inc. While the publisher and the author have used good faith efforts to ensure that the information and instructions contained in this work are accurate, the publisher and the author disclaim all responsibility for errors or omissions, including without limi‐ tation responsibility for damages resulting from the use of or reliance on this work. Use of the information and instructions contained in this work is at your own risk. If any code samples or other technology this work contains or describes is subject to open source licenses or the intellectual property rights of others, it is your responsi‐ bility to ensure that your use thereof complies with such licenses and/or rights.
    [Show full text]
  • Conceptual Architecture Patterns
    HASSO - PLATTNER - INSTITUT für Softwaresystemtechnik an der Universität Potsdam Conceptual Architecture Patterns Technische Berichte des Hasso-Plattner-Instituts für Softwaresystemtechnik an der Universität Potsdam Technische Berichte des Hasso-Plattner-Instituts für Softwaresystemtechnik an der Universität Potsdam 2 Conceptual Architecture Patterns: FMC-based Representations Bernhard Gröne and Frank Keller (eds.) April 2004 Bibliografische Information Der Deutschen Bibliothek Die Deutsche Bibliothek verzeichnet diese Publikation in der Deutschen Nationalbibliografie; detaillierte bibliografische Daten sind im Internet über http://dnb.ddb.de abrufbar. Die Reihe Technische Berichte des Hasso-Plattner-Instituts für Softwaresystemtechnik an der Universität Potsdam erscheint aperiodisch. Herausgeber: Professoren des Hasso-Plattner-Instituts für Softwaresystemtechnik an der Universität Potsdam Redaktion Bernhard Gröne und Frank Keller EMail {bernhard.groene, frank.keller}@hpi.uni-potsdam.de Vertrieb: Universitätsverlag Potsdam Postfach 60 15 53 14415 Potsdam Fon +49 (0) 331 977 4517 Fax +49 (0) 331 977 4625 e-mail: [email protected] http://info.ub.uni-potsdam.de/verlag.htm Druck allprintmedia gmbH Blomberger Weg 6a 13437 Berlin email: [email protected] © Hasso-Plattner-Institut für Softwaresystemtechnik an der Universität Potsdam, 2004 Dieses Manuskript ist urheberrechtlich geschützt. Es darf ohne vorherige Genehmigung der Herausgeber nicht vervielfältigt werden. Heft 2 (2004) ISBN 3-935024-98-3 ISSN 1613-5652 Conceptual Architecture Patterns: FMC–based Representations Bernhard Gröne and Frank Keller (editors) Research assistants of the chair “Modeling of Software–intensive Systems” Hasso–Plattner–Institute for Software Systems Engineering P.O. Box 900460, 14440 Potsdam, Germany E-mail: {bernhard.groene, frank.keller}@hpi.uni-potsdam.de Abstract This document presents the results of the seminar “Conceptual Architecture Patterns” of the winter term 2002 in the Hasso–Plattner–Institute.
    [Show full text]
  • Middleware Architecture with Patterns and Frameworks
    Middleware Architecture with Patterns and Frameworks Sacha Krakowiak Distributed under a Creative Commons license http://creativecommons.org/licenses/by-nc-nd/3.0/ February 27, 2009 Contents Preface ix References........................................ x 1 An Introduction to Middleware 1-1 1.1 Motivation for Middleware . 1-1 1.2 CategoriesofMiddleware . 1-6 1.3 A Simple Instance of Middleware: Remote Procedure Call . ......... 1-7 1.3.1 Motivations and Requirements . 1-8 1.3.2 Implementation Principles . 1-9 1.3.3 Developing Applications with RPC . 1-11 1.3.4 SummaryandConclusions. .1-13 1.4 Issues and Challenges in Middleware Design . 1-14 1.4.1 DesignIssues ...............................1-14 1.4.2 Architectural Guidelines . 1-15 1.4.3 Challenges ................................1-17 1.5 HistoricalNote .................................. 1-18 References........................................1-19 2 Middleware Principles and Basic Patterns 2-1 2.1 ServicesandInterfaces . 2-1 2.1.1 Basic Interaction Mechanisms . 2-2 2.1.2 Interfaces ................................. 2-3 2.1.3 Contracts and Interface Conformance . 2-5 2.2 ArchitecturalPatterns . 2-9 2.2.1 Multilevel Architectures . 2-9 2.2.2 DistributedObjects . .. .. .. .. .. .. .. .2-12 2.3 Patterns for Distributed Object Middleware . 2-15 2.3.1 Proxy ...................................2-15 2.3.2 Factory ..................................2-16 2.3.3 Adapter..................................2-18 2.3.4 Interceptor ................................2-19 2.3.5 Comparing and Combining Patterns . 2-20 2.4 Achieving Adaptability and Separation of Concerns . ..........2-21 2.4.1 Meta-ObjectProtocols. 2-21 2.4.2 Aspect-Oriented Programming . 2-23 ii CONTENTS 2.4.3 PragmaticApproaches. .2-25 2.4.4 ComparingApproaches .
    [Show full text]
  • Adaptivity of Business Process
    ICONS 2013 : The Eighth International Conference on Systems Adaptivity of Business Process Charif Mahmoudi Fabrice Mourlin Laboratory of Algorithms, Complexity and Logics, Laboratory of Algorithms, Complexity and Logics, Paris 12th University Paris 12th University Créteil, France Creteil, France [email protected] [email protected] Abstract— Enterprise service bus is a software architecture local services is less costly in a number of messages than a middleware used for implementing the interaction between business process using remote services. Blockings are also software applications in a Service Oriented Architecture. We less numerous, and, therefore, the execution of a business have developed a strategy to dynamically manage business process is more efficient. processes. Administrators of service bus need to reconfigure This remark highlights the dependencies between two sites where the business processes are placed. This evolution concepts, the location of business processes and its own has to be done during execution of service through the bus. We definition. The designer should not consider his work in the ensure the availability of process definition. Moreover, placement constraints. In addition, the administrator cannot business process can also be autonomous. This means a process take into account all the dependencies of a process definition which is able to move from one site to another one, where the to find a better placement. Also, our second point is: how business process engine is installed. This provides another approach to design business process. With our "mobile process separate the two. These conclusions led us to consider an migration" template, we separate two concerns, on one side initial configuration of business processes is not satisfactory.
    [Show full text]
  • 623 a Abfangen Temporärer Fehler, 479 Abgesicherter
    Index A allow_url_fopen, 510 allow_url_include, 510 Abfangen temporärer Fehler, 479 Amazon.com, 409 abgesicherter monolithischer Kernel, 135 Ambient Authority, 99, 107, 158, 416, 446 ablaufbasierte Kontrolle, 104 Ambige Interfaces, 476 Abschalten von Javascript, 503 Analysis/Paralysis Pattern, 553 Absichern von Application-Servern, 347 Anfangs- bzw. Endspanne, 571 Absicherung der Ressourcen, 350 Angriffe Absicherung der Verbindungen, 349 Klassifikation, 12 Absicherung von Servern, 169 Angriffsformen Abwehr auf der Netzwerkschicht, 39 lokale, 15 Access Control Context, 95, 203, 214 Anreicherung von Privilegien, 152 Access Control Lists, 108, 118 Antipattern, 99, 473 Access Control Markup Language, 197 API in Form paarweiser Methoden, 509 Access Control Matrix, 564 Append-Only-Recht, 152 Access Control Policies, 195 Application Integration in Acegi, 295 SSO-Infrastruktur, 285 ACL, 108, 118, 291 Application Level Security, 262 Beispiel, 119 Application Server Malware, 119 LTPA, 335 Solitaire, 119 Application Server Security, 313 Active Object, 470 Application Tower, 230 Add-Ons, 445 Application-Server, 330 Administration, 174 Architektur, 318 Administrationsfunktion, 288 Authorisierungscode in der „after the fact“-Sicherheitsmechanismen, Applikation, 329 417 Beispielarchitektur, 320 AJAX, 69 Classloader, 325 Java Script Object Notation, 75 Concurrency, 316 On-Demand JavaScript, 74 Credentials für den Zugriff auf Techniken, 72 Backends, 329 XMLHttpRequest, 72 CSIv2, 318 aktionsintegrierte Sicherheit, 554 Delegation mit Neuerzeugung Alias-Antipattern,
    [Show full text]