1 / 23

TIB RV Concept and Usage in Polaris

TIB RV Concept and Usage in Polaris. Neo Yao IT Department Polaris Financial Group 2005/01/18. Content. Introduction TIB RV Concept Usage in Polaris Future plan Q&A. Introduction. For modern design of system, many machines or process will work together for a complex task.

keon
Download Presentation

TIB RV Concept and Usage in Polaris

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. TIB RV Concept and Usage in Polaris Neo Yao IT Department Polaris Financial Group2005/01/18

  2. Content • Introduction • TIB RV Concept • Usage in Polaris • Future plan • Q&A

  3. Introduction • For modern design of system, many machines or process will work together for a complex task. • But communication in distributed system become a heavy overhead. • It’s a good idea to introduced a middleware between frontend and backend components. • TIB RV is one kind of middleware besides MQSeries, BizTalk.

  4. TIB RV Concept • Basic: • Asynchronous • Event-Driven (Real-time) • Subject-Oriented • Loosely Coupled (Publish-Subscribe) • Multicast & point-to-point • Self-describing data • Machine Independence

  5. Benefit of TIB RV • No need know client or server address (good for distributed program) • Multi-thread safe • Publish multicast message quickly and reliability • Request/reply support • Location independent, easy to migrate • Smoothly to expand

  6. Server Client Demand Driven • Traditional Client-Server Architecture Request Reply

  7. Publisher Subscriber Subscriber Event-Driven • Subscribers will get an event notification at the same time right after message publish out. Notification TIBRV

  8. Publisher Subscriber Subscriber Subscriber Subject Oriented • Subscriber will not receive any un-interested subject message notification. stock.ibm stock.ibm stock.dec stock.ibm Notification TIBRV

  9. Subject Oriented • Applications publish data on the TIB under a semantically meaningful subject • Applications subscribe to subjects and receive all data published under those subjects • Subject-based addressing provides location transparency

  10. Product.Spec Product: Status: Approved Author: John Instructions: special Paradigm THE INFORMATION BUS Order.New.Asia.Japan Factory.Line.Yield Yield: 80% Time: 9/25/94 Comments: on track Customer: Price: 79 Qty: 2000 Area.Equip.Status.Up Name: Status: Up Recipe: XYZ Comments: went down due to malfunction

  11. TIB Architecture Appl. 1 Appl. 2 Appl. 3 Appl. 4 TCP TCP TCP TCP RVD RVD Reliable UDP Multicast RVD TCP TCP Appl. 5 Appl. 6

  12. TIB RV Daemon • Daemon rvd, a background process for rv message communication • Runs on the same machine of AP • AP connect to RVD with TCP protocol • RVD communicate with other RVD with UDP • RVD handle for AP:the details of data transport, packet ordering, receipt acknowledgment, retransmission requests, and dispatching information to the correct program processes. • One RVD is enough for a machine.

  13. RVD Parameter • Daemon : Tcp communication port between RVD & AP, tcp:port or tcp:host_ip:port (remote deamon)example: “tcp:7500” (default), “tcp:server1:7500” • Network : Multicast address “;224.0.0.0” ~ “;239.255.255.255”; • Service:UDP service port between RVD and other RVDexample: 7500 (default), 8000

  14. RVD Parameter • Two AP on different machines need to communicate must has same network & service parameter. • One service number only can bind to one network parameter in a machine • Default “”, “”, “” “tcp:7500”, broadcast, “7500”

  15. TIB Concept • Advance: • 保証送達 Certificated Message (RVCM) • 分工模式 Distributed Queue (RVDQ) • 成對備援 Fault Tolerant (RVFT) • 跨網段路由器 Routing Daemon (RVRD)

  16. TIB RV/CM • Use for important message delivery like order or transaction. All message keep by sender’s transport for retransmit before listener confirmation. • Registration (sender auto allow listener’s request) • Certified Delivery Agreement - Sender keep outbound message - Listener confirm after received • Ledge file (memory or file)

  17. Support platform/language • HP/UX, Solaris / C, Java • MS Windows / C/C++, COM, Java • OS/400, AIX / C, Java • FreeBSD, Linux/ C, Java • VMS/ C • Download RV:http://www.tibco.com/solutions/products/active_enterprise/rv/default.jsp* Request a licence first to get a month free try.

  18. Usage in Polaris TW • Reuters real-time quote (before 2004 Aug.) Reuters DC MDDS TIBRV Chart DB Streaming Server SSL COM Polaris Quote/News AP Finairport Quote/News ASP EQ Java Applet

  19. Usage in Polaris TW • Back-office Publish TMOL-EQ All order transaction TIB RV/CM RV COM API RV2Tandem AP Tandem Backoffice

  20. Usage in Polaris TW • EQ & Finairport Single-Sign-on EQ FrontendTokenserver User sign-on, sign-off TIB RV + RVRD RV COM API SingleSignon AP User sign-on, sign-off, token Finairport Authentication Server Web user

  21. Usage in Polaris HK • RVXIA between HKFIX & HKBSS TMOL EQ TIB RV/CM TWFIX Taiwan HK FIX HKFIX TIB RV/CM HKBSS ISPI RV C++ API RVXIA mtalk

  22. Usage in Polaris HK (Future) • RV2eBroker between HKFIX & eBroker TMOL EQ TIB RV/CM TWFIX Taiwan HK FIX HKFIX TIB RV/CM HKBSS eBroker RV API RV2eBroker eBroker API

  23. Q & A Thanks!

More Related