Welcome to the InfoSci Platform
Reference Hub1
Reengineering and Wrapping Legacy Modules for Reuse as Web Services: Motivation, Method, Tools, and Case Studies

Reengineering and Wrapping Legacy Modules for Reuse as Web Services: Motivation, Method, Tools, and Case Studies

Harry M. Sneed
Copyright: © 2013 |Pages: 31
ISBN13: 9781466624887|ISBN10: 1466624884|EISBN13: 9781466624894
DOI: 10.4018/978-1-4666-2488-7.ch004
Cite Chapter Cite Chapter

MLA

Sneed, Harry M. "Reengineering and Wrapping Legacy Modules for Reuse as Web Services: Motivation, Method, Tools, and Case Studies." Migrating Legacy Applications: Challenges in Service Oriented Architecture and Cloud Computing Environments, edited by Anca Daniela Ionita, et al., IGI Global, 2013, pp. 71-101. https://doi.org/10.4018/978-1-4666-2488-7.ch004

APA

Sneed, H. M. (2013). Reengineering and Wrapping Legacy Modules for Reuse as Web Services: Motivation, Method, Tools, and Case Studies. In A. Ionita, M. Litoiu, & G. Lewis (Eds.), Migrating Legacy Applications: Challenges in Service Oriented Architecture and Cloud Computing Environments (pp. 71-101). IGI Global. https://doi.org/10.4018/978-1-4666-2488-7.ch004

Chicago

Sneed, Harry M. "Reengineering and Wrapping Legacy Modules for Reuse as Web Services: Motivation, Method, Tools, and Case Studies." In Migrating Legacy Applications: Challenges in Service Oriented Architecture and Cloud Computing Environments, edited by Anca Daniela Ionita, Marin Litoiu, and Grace Lewis, 71-101. Hershey, PA: IGI Global, 2013. https://doi.org/10.4018/978-1-4666-2488-7.ch004

Export Reference

Mendeley
Favorite

Abstract

This chapter deals with how this reengineering can be done. The goal is to make modular, flexible, and independent Web services from the monolithic, rigid, and dependent legacy modules. The methods used to achieve this goal are static analysis, code restructuring, code stripping, code transformation, and code wrapping. The legacy code can be either left in a procedural form in the original language or translated to an object-oriented architecture in the Java language. The result is in both cases an independent, wrapped service with a standard WSDL interface and a separate database access shell. All of the steps of the migration process are supported by automated tools. The wrapped services are available to all applications capable of sending and receiving SOAP messages. The automated process described here has been successfully applied in three industrial migration projects. The experience gained in those projects is discussed at the end of the chapter.

Request Access

You do not own this content. Please login to recommend this title to your institution's librarian or purchase it from the IGI Global bookstore.