The Architecture Framework with Exception Handing in SOA

2010 ◽  
Vol 20-23 ◽  
pp. 992-997 ◽  
Author(s):  
Qing Wu ◽  
Shi Ying ◽  
You Cong Ni ◽  
Hua Cui
Keyword(s):  
Exception Handling ◽  
Software Systems ◽  
Separation Of Concerns ◽  
Clear Separation ◽  
Reliable Service ◽  
Architecture Framework ◽  
Service Oriented ◽  
Business Function ◽  
Oriented System

Service-oriented software systems are inherently complex and have to cope with an increasing number of exceptional conditions in order to meet the system’s dynamic requirements. This work proposes an architecture framework which has exception handling capability. This framework ensures the credibility of service-oriented software, during the architectural stage, by adding exception handling-related architecture elements and modeling exception handling process. It allows a clear separation of concerns between the business function and the exception handling unit, using reflection mechanism. It plays an important guiding role for achieving reliable service-oriented system.

Addressing Highly Dynamic Changes in Service-Oriented Systems

2013 ◽  
pp. 33-46 ◽  
Author(s):  
Andreas Metzger ◽  
Elisabetta Di Nitto
Keyword(s):  
Life Cycle ◽  
Service Life ◽  
Historical Development ◽  
Software Systems ◽  
Life Cycle Model ◽  
Service Oriented ◽  
Reference Service ◽  
Self Adaptation ◽  
Service Life Cycle ◽  
Oriented System

This chapter sets out to introduce relevant foundations concerning evolution and adaptation of service-oriented systems. It starts by sketching the historical development of software systems from monolithic and mostly static applications to highly-dynamic, service-oriented systems. Then, it provides an overview and more thorough explanation of the various kinds of changes that may need to be faced by service-oriented systems. To understand how such changes could be addressed, the chapter introduces a reference service life-cycle model which distinguishes between evolution, viz. the manual modification of the specification and implementation of the system during design-time, and (self-)adaptation, viz. the autonomous modification of a service-oriented system during operation. Based on the discussion of the key activities prescribed by that life-cycle, the chapter elaborates on the need for agility in both adaptation and evolution of service-oriented systems.

A Platform for Analyzing Behaviors of Service-Oriented Application Based on the Probabilistic Model Checking

2015 ◽  
Vol 3 (2) ◽  
pp. 24-38 ◽  
Author(s):  
Jinyu Kai ◽  
Huaikou Miao ◽  
Kun Zhao ◽  
Jiaan Zhou ◽  
Honghao Gao
Keyword(s):  
Model Checking ◽  
Web Service ◽  
Probabilistic Model ◽  
Probabilistic Model Checking ◽  
Software Systems ◽  
Model Checker ◽  
System Behavior ◽  
Service Oriented ◽  
The Web ◽  
Oriented System

Service oriented software systems running in a highly open, dynamic and unpredictable Internet environment are inevitable to face all kinds of uncertainty. To monitor the operation of the web services system behavior analysis and analysis whether the system behavior is consistent with the requirements is the basis to determine whether the system needs to be reconfigured. In this paper, an analytical platform for the behavior of a web service-oriented system based on the probabilistic model checking is introduced which provides the basis for judging whether a system needs to be reconfigured by applying the approach of probabilistic model checking to verify whether the behavior system model is satisfied requirement properties. This platform is implemented in Java language and using the dot tool that the Graphviz provides and the PRISM model checker to construct the behavior model of the web service-oriented system based on web log files, to view and edit behavior models visually, and to convert the model from one form to another to make it convenience for users to use the model checker PRISM. Finally, we can judge whether the model is satisfied the desired requirements according to the verification result.

Addressing Highly Dynamic Changes in Service-Oriented Systems

2014 ◽  
pp. 164-177 ◽  
Author(s):  
Andreas Metzger ◽  
Elisabetta Di Nitto
Keyword(s):  
Life Cycle ◽  
Service Life ◽  
Historical Development ◽  
Software Systems ◽  
Life Cycle Model ◽  
Service Oriented ◽  
Reference Service ◽  
Self Adaptation ◽  
Service Life Cycle ◽  
Oriented System

This chapter sets out to introduce relevant foundations concerning evolution and adaptation of service-oriented systems. It starts by sketching the historical development of software systems from monolithic and mostly static applications to highly-dynamic, service-oriented systems. Then, it provides an overview and more thorough explanation of the various kinds of changes that may need to be faced by service-oriented systems. To understand how such changes could be addressed, the chapter introduces a reference service life-cycle model which distinguishes between evolution, viz. the manual modification of the specification and implementation of the system during design-time, and (self-)adaptation, viz. the autonomous modification of a service-oriented system during operation. Based on the discussion of the key activities prescribed by that life-cycle, the chapter elaborates on the need for agility in both adaptation and evolution of service-oriented systems.

Distributed Business Rules within Service-Centric Systems

2010 ◽  
pp. 448-470
Author(s):  
Florian Rosenberg ◽  
Anton Michlmayr ◽  
Christoph Nagl ◽  
Schahram Dustdar
Keyword(s):  
Business Processes ◽  
Communication Protocols ◽  
The Other ◽  
Software Systems ◽  
Business Rules ◽  
Clear Separation ◽  
Server Side ◽  
The Core ◽  
Service Oriented ◽  
Software Services

Business rules enable a clear separation of concerns between the core business knowledge and the underlying application code. Service-oriented Computing, on the other side, enables flexible software systems and provides support for business processes based on software services with well-defined interface, descriptions and communication protocols. Yet, the alignment of software services and business rules has not been addressed in literature. In this chapter we present the ViDRE system that bridges the gap between these two paradigms by exposing business rules as Web services. In contrast to existing rule engines, our approach supports distributed rule execution using meta-rules which includes automatic transformation of rules on both client- and server-side.

Exception Throwing Analysis and Exception Handling Method for BPEL

2014 ◽  
Vol 1030-1032 ◽  
pp. 1905-1908
Author(s):  
Yue Hua Ding ◽  
Ri Hua Xiang
Keyword(s):  
Fault Tolerance ◽  
Process Development ◽  
Fault Tolerant ◽  
Exception Handling ◽  
Business Logic ◽  
Service Oriented ◽  
Handling Mechanism ◽  
Chain Theory ◽  
Handling Method ◽  
Oriented System

Business developer needs to develop fault-tolerant process, but fault-tolerant process development based on exception handling mechanism provided by BPEL costs much time and is easy to make mistake. We analyze application exception throw chain theory of service-oriented system. Exception throwing of BPEL process is broadcasted among component layer, service layer and process layer. We also propose an application exception handling method for BPEL by using EHPDL-P. EHPDL-P can separate normal business logic and exception business logic, and thus it can enhance BPEL fault-tolerance ability.

A Two Phases Self-healing Framework for Service-oriented Systems

2021 ◽  
Vol 15 (2) ◽  
pp. 1-25
Author(s):  
Amal Alhosban ◽  
Zaki Malik ◽  
Khayyam Hashmi ◽  
Brahim Medjahed ◽  
Hassan Al-Ababneh
Keyword(s):  
Web Services ◽  
A Priori ◽  
Fault Management ◽  
Service Selection ◽  
Exception Handling ◽  
Self Healing ◽  
Service Oriented Architectures ◽  
Service Oriented ◽  
Improved Performance ◽  
High Level

Service-Oriented Architectures (SOA) enable the automatic creation of business applications from independently developed and deployed Web services. As Web services are inherently a priori unknown, how to deliver reliable Web services compositions is a significant and challenging problem. Services involved in an SOA often do not operate under a single processing environment and need to communicate using different protocols over a network. Under such conditions, designing a fault management system that is both efficient and extensible is a challenging task. In this article, we propose SFSS, a self-healing framework for SOA fault management. SFSS is predicting, identifying, and solving faults in SOAs. In SFSS, we identified a set of high-level exception handling strategies based on the QoS performances of different component services and the preferences articled by the service consumers. Multiple recovery plans are generated and evaluated according to the performance of the selected component services, and then we execute the best recovery plan. We assess the overall user dependence (i.e., the service is independent of other services) using the generated plan and the available invocation information of the component services. Due to the experiment results, the given technique enhances the service selection quality by choosing the services that have the highest score and betters the overall system performance. The experiment results indicate the applicability of SFSS and show improved performance in comparison to similar approaches.

scholarly journals Composition, Separation of Roles and Model-Driven Approaches as Enabler of a Robotics Software Ecosystem

2020 ◽  
pp. 53-108
Author(s):  
Christian Schlegel ◽  
Alex Lotz ◽  
Matthias Lutz ◽  
Dennis Stampfer
Keyword(s):  
Complex Systems ◽  
Open Source ◽  
Building Block ◽  
Building Blocks ◽  
Software Systems ◽  
Software Components ◽  
Separation Of Concerns ◽  
Software Ecosystem ◽  
Model Driven ◽  
Successful Approach

AbstractSuccessful engineering principles for building software systems rely on the separation of concerns for mastering complexity. However, just working on different concerns of a system in a collaborative way is not good enough for economically feasible tailored solutions. A successful approach for this is the composition of complex systems out of commodity building blocks. These come as is and can be represented as blocks with ports via data sheets. Data sheets are models and allow a proper selection and configuration as well as the prediction of the behavior of a building block in a specific context. This chapter explains how model-driven approaches can be used to support separation of roles and composition for robotics software systems. The models, open-source tools, open-source robotics software components and fully deployable robotics software systems shape a robotics software ecosystem.

scholarly journals Research on Service-Oriented Software Systems and Computer Software and Intelligent Calculation Method

2021 ◽  
Vol 2083 (3) ◽  
pp. 032095
Author(s):  
Zhimin Ni ◽  
Fan Zhao
Keyword(s):  
Software Development ◽  
Calculation Method ◽  
Computer Software ◽  
Technical Support ◽  
Software Systems ◽  
Timely Manner ◽  
Software Failure ◽  
Business Software ◽  
Service Oriented ◽  
Software Business

Abstract For the existing service-oriented software single, favors business processing, cannot guarantee the software business processing into the development of software. When the operator encounters operational problems, software failure problems and other problems related to software operation and operation, software development technicians to provide technical support to ensure the software’s business processing functions. This study will move away from dependence on other software and provide technical support to business software operators accurately and in a timely manner to effectively solve the problems that operators may encounter.

Sign in / Sign up

Export Citation Format

Share Document