A proven Java(TM)-based approach to standardizing and streamlining legacy migration
This book focuses on the key challenges developers face when using the Java 2 platform Enterprise Edition (J2EE) to encapsulate legacy applications for delivery in a multi-tier Internet environment. Leading Sun architects Torbjoern Dahlen and Thorbioern Fritzon show how to standardize encapsulation using an integration tier that shields the J2EE elements of an application from the properties and demands of its legacy elements. Using this approach, enterprises can promote reuse, accelerate legacy migration projects, and make the most of their COBOL/mainframe and Java expertise. Above all, they can take portability beyond hardware and operating systems, systematically migrating virtually any legacy system without extensive redesign or reprogramming.
- Presents a pragmatic approach to domain modeling for legacy application migration
- Promotes reuse and portability through a standardized, fine-grained domain object model
- Shows how to streamline the transformation of domain models to working systems
- Introduces a proven, pattern-based J2EE application architecture for Internet-enabling legacy systems
- Includes superior algorithms for object queries, data cleansing and merging, and artificial XA support
Advanced J2EE Platform Development presents detailed examples and sample code, including a start-to-finish case study that demonstrates integration between three different legacy systems.
|Product dimensions:||7.03(w) x 9.25(h) x 0.55(d)|
About the Author
TORBJOeRN DAHLEN, chief architect at the Wireless Solution Center in Sun Microsystems' Professional Services division, specializes in J2EE-based telecom and financial applications. Before joining Sun in 1997, he worked with distributed systems and CORBA at Ericsson in Sweden. As a member of Sun Services Technology Council, he belongs to a network of leading technologists within Sun's worldwide services organization. He is an appreciated speaker at JavaOne and writes articles on J2EE for Java Report magazine.
THORBIOeRN FRITZON is a Java architect for Sun Microsystems with more than a decade of experience in software development, mostly in distributed systems.
Table of Contents
1. Domain Modeling.
Creating a Common Domain Model. Summary.
2. Design Modeling.
Creating a Design Model. Design Guidelines. Summary.
3. Implementing the Integration Tier.
Legacy System Background. The Consequences of Legacy System Architecture. Managing Distributed Transactions. Data Merging. Object Query Management. Implementation of Data Access Objects. Summary.
4. Legacy System Integration.
The Common Domain Model. The Design Model. Legacy System Service Mappings. Managing Transactions. Summary.
5. Application Development.
Extending the Common Domain Model. Application Development. Summary.
B: Hypothetical Legacy Systems.
This book is the result of a series of Java 2(TM) Platform Enterprise Edition (J2EE(TM)) application development projects we conducted for Sun Microsystems, Inc.'s customers in Sweden between 1998 and 2001.
During the course of these projects, it became apparent to us that legacy system integration is very much an ad hoc operation. It was equally clear that many object-oriented application development projects fail to use domain models.These factors drove us to write this book. Our purpose is to share the best practices and techniques we had to develop for ourselves in order to execute these projects. We hope that readers of this book will benefit from and further enhance the ideas presented, and that J2EE Platform-based application development and legacy system integration will become less ad hoc and more firmly based on such methods and best practices in the future.
This book does not provide any defined solutions or silver bullets. Integrating J2EE Platform applications with legacy systems is a difficult task that requires a thorough understanding of both legacy system applications and object-oriented design. We have tried to find a practical approach to applying the J2EE integration tier patterns in real-world situations, the main design principle being that of separation of concerns. Some of the designs described in this book are currently running in production, while others represent theoretical work that has not yet been tested in a full-scale production environment. We hope, however, that in reading this book you will gain valuable tools with which to start the long journey toward application integration.
Because our customers have often expressed a need for reduced mainframe dependency and an increasing requirement for rapid redeployment of J2EE Platform applications together with different legacy systems, we have coined the term "application portability across enterprise information systems." By this we mean that a J2EE Platform application should appear to be "portable," that is, easily redeployed with a new legacy system with minimal effort devoted to changing any of the design or Java(TM) code. We believe that by applying the ideas presented in this book, you can achieve this "portability."
All designs and solutions presented here are driven entirely by actual customer requirements. This book describes a reality faced every day by thousands of J2EE developers at banks, telecom operators, and so on. We wish all of them the best in their countless hours of effort in building bridges between today's technology and the legacy world.