Migrating Legacy Systems to Web Services Architecture

Migrating Legacy Systems to Web Services Architecture

Shing-Han Li (Tatung University, Taiwan), Shi-Ming Huang (National Chung Cheng University, Taiwan), David C. Yen (Miami University, USA) and Cheng-Chun Chang (National Chung Cheng University, Taiwan)
DOI: 10.4018/978-1-60566-172-8.ch015
OnDemand PDF Download:


The lifecycle of information system (IS) became relatively shorter compared with earlier days as a result of information technology (IT) revolution and advancement. It is tremendous difficult for an old architecture to catch up with the dynamic changes occurred in the market. To match with the fast pace of challenges, enterprises have to use the technology/concept of information system reengineering (ISR) to preserve the value of their legacy systems. Consequently, web services-based systems with Service- Oriented Architecture (SOA) are widely accepted as one of the possible solutions for an enterprise information system to retain/keep its old legacy systems. Using this aforementioned architecture, enterprise information systems tend to be more flexible and agile to fit into the capricious business environment, and thus, be easier to integrate with additional applications. In other words, it is indeed an essential requirement for an enterprise to establish such a system to further improve corporation’s productivity and operational efficiency. In specific, the requirement is simply to migrate the legacy systems to be SOA architecture. However, it is a trade-off between the value of legacy systems and the compatibility with SOA to decide whether this alternative is a feasible one. The purpose of this manuscript is to propose a migrating solution to convert the architecture of the legacy system into SOA with a systematic approach. This proposed methodology is different from the traditional object-oriented approaches, which migrates the system to have a services-oriented focus without incorporating general objected-oriented (OO) or functional oriented feature. In this study, a case study and information capacity theory were employed to verify/validate that this approach is indeed an effective and a practicable one.
Chapter Preview


Due to the dynamic advancement of information technology (IT), the life cycle of the information system (IS) is greatly reduced to a certain extent. Generally speaking, the traditional legacy information systems possess such undesirable characteristics as latency of information, poor reach, inflexibility, and higher cost of maintenance. Furthermore, the traditional system architectures such as centralized and client/server are frequently incompatible with the requirements and specifications which exist in today’s business environment. To be more specific, the legacy information systems have these aforementioned shortcomings, which have prevented the businesses and/or organizations to react/respond dynamically to the rapid challenges as they should. Consequently, enterprises have a strong need to utilize the technology of information system reengineering (ISR) to preserve the value of their legacy systems.

In this situation, enterprises or software companies are always in a dilemma of redeveloping/redesigning their legacy systems to include the newer Web services components (Bouguettaya, Malik, Rezgui, & Korff, 2006; Chen, Zhou, & Zhang, 2006; Kim, Sengupta, Fox, & Dalkilic, 2007). Discarding and redeveloping the existing systems not only wastes the money allocated for software investments, but also causes organizations to lose competitive advantages to meet numerous unanticipated contingencies and/or uncertainties.

Based on prior study (Ommering, 2005), the system migration will be one of the best ways to reengineer a legacy system. Traditionally, there are two approaches available to migrate the legacy system to the Web services architecture (Vanston, 2005). The first approach is the legacy externalization approach. This approach is usually the main alternative available on the current market. It generally uses strategic or pointed forms, along with new types of interface display, to develop the integrated products (such as “Web Scraping”). The other approach is the component encapsulation approach. This is another viable alternative to utilize the component standard technology like Common Object Request Broker Architecture (CORBA) (OMG, 1995; Vinoski, 1997), Component Object Model (COM) (Microsoft, 2007), or Enterprise Java Beans (EJB) (Sun, 2007) to encapsulate the legacy system into the components, and then translate them into a Web Services standard. Ultimately, this second approach is migrated to the component-based and transaction-oriented framework (such as IBM WebSphere and BEA WebLogic) (Liu, Fekete, & Gorton, 2005; Waguespack & Schiano, 2004). Both of the aforementioned approaches may not be a bad way for the legacy system to migrate into the equivalent Web services standards. However, they normally utilize the hard-cording technique to implement the interface with the corresponding standard (Brereton & Budgen, 2000; Kwan & Li, 1999; McArthur, Saiedian, & Zand, 2002). Being a traditional structure program, the system normally has a shorter life cycle and lacks scalability, feasibility, and reusability. Further, it would be much more difficult to maintain in the future. On the other hand, if a company is applying the component encapsulation approach without incorporating appropriate component migrating methods, the system still has these aforementioned shortcomings (Rahayu, Chang, Dillon, & Taniar, 2000). Unfortunately, most alternatives adopted now by enterprises and/or businesses do not use the proper component migrating method.

Complete Chapter List

Search this Book: