1 / 27

Demonstration of Internet Booking Service with CORBA Distributed Transactions

Explore the implementation of an integrated transaction service system using CORBA for a distributed network, focusing on resource sharing, scalability, and fault tolerance.

dstephen
Download Presentation

Demonstration of Internet Booking Service with CORBA Distributed Transactions

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Booking Service on Internet to Demonstrate Distributed Transaction on CORBA Presented by Kam Shu Kai, Andy Student No.: 97082720 Supervisor : Professor Michael R. Lyu

  2. Content • Motivation • Distributed System • CORBA • Implementation: Integrated Transaction Service System • Conclusion

  3. Motivation • Network technology • Client/Server Distributed system VS Centralized system • OMG/ORB • Integrated Transaction Service System

  4. Distributed System(1) • Personal computers and Workstations • Local Area Networks • Database server • WWW

  5. Distributed System(2) • Key Characteristics • Resource Sharing • Openness • Concurrency • Scalability • fault tolerance • transparency

  6. Distributed System(3) • Basic Design Issues • Naming • Communication • Workload allocation • Consistency maintenance

  7. CORBA (1) • Object Management Architecture

  8. CORBA (2) • CORBA ORB • Static and dynamic method invocation • High-level language bindings • Self-describing system • Local/remote transparency • Built-in security and transactions

  9. CORBA (3) • Client side • Client IDL stubs • Dynamic Invocation Interface (DII) • Interface Repository APIs • ORB Interface

  10. CORBA (4) • Server side • Server IDL Skeleton • Dynamic Skeleton Interface (DSI) • Object Adapter • Interface Repository • ORB Interface

  11. Demonstration (1) • System Requirement (1) • Transaction on Internet - Web browser • Venue Booking and Service Adding • Seat Reservation • Multiple users • Quick response time

  12. Demonstration (2) • System Requirement (2) • View the updated/inserted record • Delete record • Notification/Error messages • Friendly GUI • Callback

  13. Demonstration (3)

  14. Demonstration (4)

  15. Implementation (1)

  16. Implementation (2) • Interface Definition Language • Module : • Client • Interface : ClientControl • InternetTran • Interface : BookDispenser, Book

  17. Implementation (3) • Database • Relational database : Oracle8 Server, Release 8.0.5.0.0 • Tables : • USERS, VENUE, ZONE • SERVICE, SESSIONS, FEE, TRANSACTIONS • Programming tools • VisiBroker for Java 3.4

  18. Implementation (4) • Communication • osagent • IIOP • Gatekeeper

  19. Objects Interaction

  20. Testing • Accuracy • functions • Performance • response time • Test strategy • Server on Solar • Client on Windows NT and Unix Workstation • 12 concurrent users

  21. Results • Concurrent update • High throughput • Enforce Business rules • Response time: • initial loading of Opening Screen • display of Seat Reservation Screen • others

  22. Discussion (1) • Accuracy and Performance • number of concurrent users ? 12 • efficiency : • No attribute in Interfaces • transfer in single a operation

  23. Discussion (2) • Design Strategy • prestart server objects • multi-server on different machines • load balancing • flexibility and reliability • thin client • UI • portability

  24. Discussion (3) • Enhancement • multiple databases on different servers • replication • fault tolerance • Object-Oriented Database • object oriented design approach • reduce the locking granularity

  25. Discussion (4) • Reusability • Scalability • Maintainability • Interoperability • Ease of use

  26. Conclusion • The best middleware: • independence of hardware platform • free choice of operation system • neutrality in programming language • openness and industrial standard • Drawbacks: • complexity • lack of visual development tools

  27. Q & A You are welcome!

More Related