• Home
• • Türkçe Anasayfa
  • Русский
  • 中文主頁
• About ASPone
• ASPone Solutions
• • Pre-Trade
  • • Feed Handlers
    • Content Integration Platform (CIP)
    • Computer Telephony Interfaces (CTI)
    • FX Rates Engine
  • Trade
  • • Order Management
  • Post-Trade
  • • Deal Entry
    • Trade/Transaction Reporting
    • Transaction Routing Hub (TRH)
  • End-to-End
  • • Historical Data Services (HDS)
• Professional Services
• • Cost Optimization and Efficiency
  • IT Consultancy
  • Product Management
  • Software Development
  • Testing and Quality Assurance
  • Project Management
• Industry News
• Managed Services
• What Our Customers Say
• Contact

End-to-End Global Network Solutions

Feed Handlers

ASPone have created a flexible and scalable approach to market data integration through the design of a re-usable software framework that allows interfaces to be developed in record time.

Reception Layer

The reception layer is responsible for providing the interface to the raw data provided by the source service, such as a direct Exchange feed or consolidated quote vendor system. The method of interfacing to the source service is governed by the physical and software protocols available for each feed on a case-by-case basis and can include APIs, libraries, tcp/ip line protocols or remote services accessed on a periodic basis.

Manipulation Layer

ASPone Feed Handlers support the reception, manipulation and forwarding of a wide range of data sources irrespective of their physical transport mediums, software protocol or architectural implementation.

Resilience: platform adapters and feed handlers are typically deployed as dual resilient pairs configured in an active-standby configuration. A failure of the active handler causes the standby handler to take over immediately, populate the system with any potentially missing data and continue its function as the new active handler.

Caching: all received data is locally cached within the Feed Manager. This allows for inter-working with target applications that supports both broadcast and interactive services. Client requests for data are passed back through the system from client–to-data source if it is not cached within other system components.

WatchList: the forwarding of data to a target system is managed through a dynamic instrument watch-list. The watch-list contains a list of instruments that are subscribed to by at least one client application and grows and reduces in size automatically as instruments are requested and de-requested.

Symbol Conversion: the Feed Manager supports a user–configurable, symbol-mapping function for converting between the source and the target system’s record and field naming conventions. This mapping capability allows source symbols to be mapped to existing symbols within the target system or a whole new set of symbols to be created outside of any existing symbol definition ranges.

Monitoring: the Feed Manager exposes an http monitoring interface, which can be “pinged” on a regular basis by remote monitoring software. The http interface provides basic adapter status information that the recipient can use to ascertain the health of the adapter e.g. current system time, last message processed time, total messages processed, messages processed/second, max buffer size/size reached etc.

Presentation Layer

Entitlements: the Feed Manager can be used in conjunction with entitlement/permissioning systems that work on either a Content or Subject basis. For Subject Based Entitlements, the Feed Manager passes symbols received from the source to the target system. In the case of Content Based Entitlements the appropriate source system entitlement code is forwarded by the Feed Manager.

Transport Interfaces: ASPone Feed Handlers support a range of transport interfaces for interfacing to third-party systems: TCP/IP, MQ, RV, JMS, RMDS etc.