 |
| |
|
|
| |
|
|
 |
 |
|
|
| |
 |
|
| |
|
|
| |
IMS is the central component of our architecture, acting both as a hub (between the exchanges and the trading applications) and as a container for trading services. |
|
| |
Its design allows any number of trading applications to make use of all the available exchange links while benefitting from all additional services. |
|
|
|
|
| |
|
|
| |
|
|
| |
• manages a user database
with configurable groups and
permissions
• supports any client protocol (FIX or proprietary)
• monitorable through JMX
|
|
|
|
|
| |
|
|
| |
|
|
| |
• connects to any number of
exchanges
• supports connecting to other IMS (cascading)
• supports transactions or market-data (or both)
|
|
|
|
|
| |
|
|
| |
|
|
| |
• allows service injection
on a global or per-connection
basis
• includes an efficient engine for services requiring
the evaluation of business rules
|
|
|
|
|
|
