Chapter One: Introduction | 第1-14页 |
·The growing complex architecture of enterprise applications | 第8-9页 |
·Service-Oriented Architecture as a Solution | 第8-9页 |
·Improve user's experience | 第9-10页 |
·Rich internet application as a solution | 第10页 |
·Introduce the RIA-SOA architecture | 第10-11页 |
·Migrating enterprise applications to RIA-SOA | 第11-12页 |
·Migrating Brower / Server applications to RIA/SOA | 第12页 |
·Thesis Organization | 第12-14页 |
Chapter Two: Related Technologies | 第14-23页 |
·Rich internet application | 第14-18页 |
·HTML/JavaScript/AJAX | 第15-16页 |
·Macromedia Flash (Flex) | 第16-17页 |
·Java (Applet, Java Web Start) | 第17-18页 |
·Microsoft Avalon | 第18页 |
·Service-Oriented Architecture | 第18-20页 |
·Benefits of Service-Oriented Architecture | 第19-20页 |
·Original system: typical B/S architecture overview | 第20-21页 |
·Target System: RIA/SOA Architecture overview | 第21-23页 |
Chapter Three: Reference model of migrating B/S application to RIA/SOA | 第23-36页 |
·Extract presentation logic | 第24-25页 |
·Present the presentation logic in use case | 第24页 |
·Remodel the user's working flow in rich | 第24-25页 |
·Extract SOA services | 第25-27页 |
·Top-down Approach and Bottom-up Approach | 第26-27页 |
·Meet-in-middle Approach is used in migrating | 第27页 |
·Choreograph SOA services and build service facade for RIA client | 第27-29页 |
·Contracts on service facade: Design by Contract | 第28-29页 |
·Rebuild the RIA client | 第29-30页 |
·Platform selection | 第29页 |
·An architecture-centric process | 第29-30页 |
·Security consideration | 第30-32页 |
·Client side security | 第30-31页 |
·Server side security | 第31-32页 |
·Performance consideration | 第32-34页 |
·Client side performance | 第33页 |
·Server side performance | 第33-34页 |
·Project management consideration | 第34-36页 |
·An initial pilot project | 第34页 |
·Iterative & incremental development model | 第34-36页 |
Chapter Four: Migration solutions & strategies | 第36-52页 |
·Choreograph service in both client side and server side | 第36-43页 |
·Programming model moves from synchronized calls in B/S to a-synchronized calls in RIA/SOA | 第36-37页 |
·Choreograph service dependences in client | 第37-42页 |
·Choreograph the services in the server | 第42页 |
·Conclusion: Divide the choreographing into both server side and client side | 第42-43页 |
·Move "session" to client | 第43-45页 |
·Strategy 1: Move the session data into one global object | 第44页 |
·Strategy 2: Distribute the session data into their related business model | 第44-45页 |
·Move upload/download files in B/S to store/load files in RIA/SOA | 第45-48页 |
·Upload / download in B/S | 第45页 |
·Store / load in RIA/SOA | 第45-46页 |
·Exception: running inside other security sandbox | 第46-48页 |
·Move foreground loading to background loading | 第48页 |
·Client side pulling in RIA/SOA application | 第48页 |
·Implement the contract on service facade by compliance test cases | 第48-52页 |
·The problem to move contracts into TTD code: Database is the central resource | 第49-50页 |
·Solutions: Make the database in a known status before any compliance check runs | 第50-52页 |
Chapter Five: Migrate a B/S data dissemination application to RIA-SOA | 第52-62页 |
·Project background | 第52-54页 |
·The limitation of the original B/S based system | 第52-53页 |
·The expectations of the target system | 第53-54页 |
·Architecture | 第54-56页 |
·Original system architecture | 第54-55页 |
·RIA technology: Flex | 第55页 |
·Target system architecture | 第55-56页 |
·The initial pilot project | 第56页 |
·Remodel the client | 第56-57页 |
·Build SOA architecture, export web service interface | 第57-58页 |
·Service definition, using 'Meet in the middle' | 第57-58页 |
·Build a new RIA frontend for end user | 第58-60页 |
·The micro-architecture developed and used in the target system | 第58-60页 |
·Automatically update from server using client pulling | 第60页 |
·Export web service API for advanced institutes | 第60-62页 |
Chapter Six: Conclusion and future work | 第62-63页 |
Reference | 第63-64页 |