Airport Enterprise Service Bus with Three Levels Self-Healing Architecture (AESB-3LSH)

Airport Enterprise Service Bus with Three Levels Self-Healing Architecture (AESB-3LSH)

Suha Afaneh (Department of Computer Science, Faculty of Information Technology, Isra University, Amman, Jordan) and Issam Al Hadid (Department of Computer Information Systems, Faculty of Information Technology, Isra University, Amman, Jordan)
DOI: 10.4018/ijstmi.2013070101
OnDemand PDF Download:
$30.00
List Price: $37.50

Abstract

This paper introduces the different aviation and airport information technology systems. Also, this paper provides Airport Enterprise Service Bus with Three Levels Self-Healing Architecture based on the Service Oriented Architecture (SOA) that improves the information accessibility and sharing across the different Airport’s departments, integrate the existing legacy systems with other applications, and improve and maximize the system’s reliability, adaptability, robustness and availability using the Self-Healing Agent, Virtual Web Service Self-Healing Connector and Extended Execution Engine with Process Execution Self-Healing Manager to guarantee the Quality of Service (QoS) or Service provided and business process execution.
Article Preview

1. Introduction

Airports need to adapt new technologies to react effectively and quickly to customers’ needs and to provide a better service such as the electronic ticket. In addition to the challenges of the ability to respond to the growing requirements of the automatic information interchange between the different systems to ensure safe and efficient airport operations. Most of the challenges in the Airport systems today lie in the ability to respond to the growing requirements of the automatic information interchange between the different departments including operational, statistical, aviation and financial information. In addition, the integration with the existing legacy systems to ensure safe and efficient airport operations. All the operations in the airport are driven by the exchanged information; Airport business units create information, transform information, distribute information, and take action on received information. Airports’ systems are developed by different vendors and were not designed to be interoperable, which makes systems integration a very complicated and not easy to be implemented. Service Oriented Architecture (SOA) provides the ability to address the distributed computing requirements; protocol independent, loosely coupled, reusability and standard based (Papazoglou & Heuvel, 2007; Keen et al., 2004; Chappell, 2005). It is based on the Web Services; distributed, loosely coupled, reusable software components that encapsulate a discrete functionality and can be accessed using standard internet and eXtensible Mark-up Language (XML)- based protocols (Sommerville, 2007; Colan, 2004; Schlimmer, 2002). SOA encourages a lot of businesses to move toward the adapting the SOA architecture to enable the response to change faster and to cut the cost of replacing the legacy systems that they have and integrate with the new systems so all the information can be accessed and shared by all the systems (Keen et al., 2004; Minoli, 2008), accordingly; SOA will provide a guideline for airport Information systems architecture design, development and integration. The functionality provided by the integration platform Enterprise Service Bus (ESB) is based on the SOA that utilizes Web service standards to supports a variety of communication patterns over multiple transport protocols to connect different applications and technologies (Papazoglou & Heuvel, 2007). In addition, the features of loosely coupling and breaking up the integration logic into separate parts can be easily managed (Keen et al., 2004). ESB provides architecture based on the SOA that improves the information accessibility and sharing across the different Airport’s departments. Furthermore, it provides a component interface to existing legacy system so it can be integrated with other applications, accessed over the web, and support the reusability of the legacy systems. Also, the Self-Healing Agents, Virtual Web Service Self-Healing Connector and Extended Execution Engine with Process Execution Self-Healing Manager which will improve and maximize the system’s reliability, adaptability, robustness and availability.

Complete Article List

Search this Journal:
Reset
Volume 3: 2 Issues (2013)
Volume 2: 2 Issues (2012)
Volume 1: 2 Issues (2011)
View Complete Journal Contents Listing