Client-tier Interaction with the MetaFluent JMS Server

The modular nature of the MetaFluent Server Framework supports the creation of server applications that combine content modeling capabilities with distribution capabilities to support downstream applications based on a variety of standard APIs and distribution protocols

Examples of different types of distribution include:

  • JMS - the MetaFluent JMS Server is a collection of modules that provides support for the MetaFluent JMS API and allows client applications to consume both managed and un-managed content as well as publish dynamic data to other JMS clients and to external systems such as RMDS
  • HTTP - An HTTP distribution adapter exposes content to browser applications as XML, CSM or other such web-friendly formats
  • RMDS - combining content adapters with RMDS distribution capability (Market Data Hub connectivity) yields an RMDS "source server" application
  • Hybrid solutions - different types of adapters can be combined to create novel solutions with multiple types of client application solutions