Event Processing and Client Push

Event processing and Client Push covers the following requirements

• Different incoming market data streams (e.g. Market Map, Bloomberg, Reuters)
• Normalization of content
• Identification of a golden copy
• Client push
  

like indicated in the following diagram

• FIX and SWIFT connectivity e.g. market data streams
• Correlation of messages arriving in time window via caching
• Message transformation to normalized format
• Rules for golden copy creation
• Client push via publish/subscribe via REST Push and
• HTML 5 messaging
  

FIX and SWIFT Connectivity

FIX connectivity can be established via the QuickFIX/J Camel Component. For details how to use this component within ISB see here.

Message Normalization

Message Transformation Applications in Stardust can be used for message normalization.

Correlation of Messages

Using Camel Aggregators

Messages can be correlated with a Camel Aggregator in a Camel Trigger for Stardust:

<aggregate>
      <correlationExpression>
        <simple>...</simple>
      </correlationExpression>
      <to uri="..."/>
</aggregate>

You may specify

• the maximum number of messages on a subject
• the length of the timeframe you are intending to wait for the aggregation

Golden Copy Creation

After all message are aggregated Java or Rules-based business logic can be provided to identify a golden copy of the message.

Client Push

Camel Websocket Component

Client push functionality can be achieved via using a Web Socket Endpoint in a Stardust Camel Application Type e.g.

websocket://hostname[:port][/resourceUri][?options]