username :
 
  password :
 
 
 

 

Recent Technological Developments >> Settlement  Server


CSTAR has been operational for the past three and half years during which not only the online trading has commenced, but in time several peripheral activities has been continuously integrated on the trading engine. As an effect the Central Trading Engine and Data Back-up Engine are responsible for carrying out several non-trading activities thereby reducing safe operating Time Window for the Trading Activity. This not only puts the following days trading in risk but also reduce the time of access by the User Groups to the ever shrinking non-trading hours. Along with the additional load on the CSTAR administrators, the Users too are deprived in terms of the various facilities that CSE Computerisation should provide them.

CSTAR is a growing application. It is evident that if the amount of growth in features and trading facilities was to be sustained in the time to come, then the time-wise resources on the Central Trading Engine and Data Back-up Engine would be further burdened when they would be required to do their House Keeping activities like Downloads, Accounting etc.

Hence the Central Computing Resource at CSE needs to be augmented by addition of DATA Server (Settlement Server) which would take certain burden off the Central trading Engine and Data-up Engine.

As a result of the tremendous growth of the CSTAR, its Administrator and Operators, both experience a burst of activities occurring along with Trading. There is practically no-room for need based rescheduling of non-trading activities since the linkages between such activities have become very intricate.

The activities that do not require the fault tolerance feature of Tandem and are not tightly coupled with trading are to be shifted to a Data Server (Settlement Server), which would take certain burden off the Central Trading Engine and Data Back-up Engine enabling better utilization of the resources, CTE and DBE. From the users end the current scenario restricts the time window during which they an participate in the non-trading activities. Not only does this become cumbersome for the various Members but the same also imposes great risk and pressure on the Administrators and Operators of the CTE and DBE.

Central activities, which are very resource intensive and do not specifically require the fault Tolerance of the Tandem Systems, are causing undue load on the trading engine. Due to the nature of such processing activities, Schedules are getting crammed up often at the risk of the following day’s trading. In view of the above the Central Computing Resources at CSE will be further strengthened by addition of a Data Server (Settlement Server) with high computing power and sufficient storage space.

The role of this Data Server (Settlement Server) would be the following :

  • Performance activities, currently done in the CTE/DBE, which do not require the fault tolerance features of Tandem (for example Settlement System etc.)
  • Those activities, which can be better, accomplished using modern tools more efficiently on comparatively inexpensive environments (for example Various Pool Accounting, Clearing House System etc.)
  • Providing facilities to the users to utilize feature of the CSTAR, which today is a part of a same schedule (for example Making Member’s query independent of Trading Schedule etc.)

Members will have this dedicated Data Server to download the Data, Report, news Releases, Notices, Masters etc. whenever they feel convenient. They will not have to be waiting for the post trading hours to carry out these activities as done today. The trading engine will not be doing these activities thereby assuring total resource availability to trading only. The Trading Schedule can thereafter be restricted to only trading related sessions, thereby reducing the number of working hours by the broker.

The Hardware and the system software has already been procured and the related application software development is one the verge of completion. The implementation of the same is expected to start shortly after the completion of the development of the application software.