OneVue integrated messaging

OneVue messaging is:

• enterprise wide,
• customised for OneVue systems,
• scalable,
• open source, 
• a proven financial services middleware standard.

OneVue messaging offers your operation:

• reduced integration costs - because one integration can communicate with multiple systems inside your organisation,
• flexibility of messaging models including: 
  • broadcast messaging - our system can send a single message to multiple destinations,
  • guaranteed delivery - because we use a 'store and forward' system, which stores messages until your recipient system is available,

  • options as to how messages are delivered and received.

• scalability enabling you to handle larger volumes and more clients - which means reduced costs and time, as well as increased reliability.

AMQP offers a proven track record. 

• It's been in use for over five years.
• It handles three million messages/day.

AMQP is now supported by:

• JP Morgan
• Credit Suisse
• Goldman Sachs
• Novell
• Cisco
• RedHat.

Advanced Messaging Queuing Protocol in detail

OneVue uses AMQP - Advanced Messaging Queuing Protocol - which is open source software developed by JP Morgan.  AMQP currently is in use at JP Morgan, generating 300 million messages per day with 2,000 concurrent users across five countries.

By complying with the AMQP standard, middleware products written for different platforms and in different languages can send messages to one another. AMQP addresses the problem of transporting value-bearing messages across and between organisations in a timely manner.

The AMQP model explicitly defines a server's semantics because interoperability demands the same semantics for any server implementation. The model specifies a modular set of components and standard rules for connecting these components. There are three main types of components which are connected into processing chains in the server to create the desired functionality:

• the 'exchange' receives messages from publisher applications and routes these to 'message queues', based on arbitrary criteria - usually message properties or content.
• the 'message queue' stores messages until they can be safely processed by a consuming client application (or multiple applications), the 'binding' defines the relationship between a message
• queue and an exchange and provides the message routing criteria.

This model emulates the classic middleware concepts of store-and-forward queues and topic subscriptions. It also expresses less trivial concepts such as content-based routing, message queue forking, and on-demand message queues.

In very general terms, an AMQP server is analogous to an email server, with each exchange acting as a message transfer agent, and each message queue as a mailbox. The bindings define the routing tables in each transfer agent. Publishers send messages to individual transfer agents, which then route the messages into mailboxes. Consumers take messages from mailboxes, which creates a simple, powerful and flexible model.