Example 4: Managing risks in financial services

A trading system needs proactive notifications of changes to customer data and securities data. For example, if the buy limit for a security is reached, information must be sent immediately to all trading systems. Currently, the securities operational database must be polled, which introduces information lag, which in turn, introduces risks to credit limit breaches. Such a system does not allow the company to take measures to evade this risk or to identify security breaches early.

At various locations, customer and securities data is stored in heterogeneous databases such as Microsoft SQL Server, Sybase ASE, and Oracle.

The current system periodically polls the database that holds credit limit thresholds resulting in performance degradation to the operational systems. The frequency of polling determines how quickly the trading company can identify whether there is a credit-limit break.

The trading company wants to automatically prevent trading once a customer’s credit limit has been reached. Polling the securities operational database is not frequent enough to accomplish this goal.

Sybase Real-Time Events pushes time-critical data from heterogeneous databases to messaging architecture, eliminating the information lags created by batch updates or intermittent polling processes.

Choose either of these:

Figure 2-4: Sybase Real-Time Events data flow

This is a Sybase Real-Time Events data flow diagram. It illustrates capture of data events in heterogeneous databases and propagation of these events to standard messaging systems. It illustrates two methods for data events capture and propagation - one using the RepConnector configuration and the other using the ASE Active Messaging. It also illustrates the development and administration capabilities provided by Sybase WorkSpace and Data Services Administrator, of the Data Integration Suite.

Data flow

When a customer places a trade request, the trading company uses Real-Time Data Services to send messages from their customer and securities databases to a message bus. The trade request is read by a client application that computes credit risk. If the credit limit is not reached, the system allows the customer’s trade. If the buy limit is reached, all trading systems connected to the message bus are immediately notified to take necessary precautionary measures.

The events are delivered to external applications in real-time through a message bus such as IBM WebSphere MQ, BEA WebLogic JMS, TIBCO EMS, or Sybase EAServer JMS.

Development

Sybase WorkSpace helps you to set up and configure the messaging service for the following:

RepConnector – RepConnector Manager plug-in configures and sets up the RepConnector.

ASE Active Messaging – Sybase WorkSpace supports ASE Active Messaging using the Database Development tool to generate SQL code that sends or receives messages from the JMS provider.

Administration

Data Services Administrator (DSA) enables you to administer the Real-Time Events component through GUI-based server managers accessible via Sybase Central plug-ins.