Abstract

Exception handling is an important issue in dependable software computing. This paper presents a system architecture and explains the role of responsibility of each component that is introduced in the architecture. The design is used to ensure the constructed service-oriented applications remain in a stable state. Service-Oriented Architecture is a paradigm for constructing current enterprise applications. It uses service composition technology to induce existing service components to provide advanced services. The most important concept in this methodology is that of reusing existing components. Business Process Execution Language (BPEL) is widely used for achieving service composition, providing basic capability for developers to deal with faults using defined activities standard in BPEL. No sufficient design, however, supports developers in implementing fault-handling components efficiently. The architecture proposed in this paper provides the design approach to explain how to reuse the fault-handling components. Additionally, the paper also provides an empirical case study that illustrates how this design was used by the Chunghwa Telecom Company in an effort to improve efficiency in implementing fault-handling components and in constructing service-oriented applications. The number of fault-handling components required was reduced from 38 to 3, implying a 92.10% efficiency rate.

Talk to us

Join us for a 30 min session where you can share your feedback and ask us any queries you have

Schedule a call

Disclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.