| |
|
|
This Process is the main post box for the message system
The Trading System cannot function without it.
This Process writes to a text file the SQL produced from the Trading System
The Trading System cannot function without it because a permanent record of all
activity must be kept.
This Process Writes The Database.
It can only function if the Sybase Service Is Active
This Process generates trades from orders
The Trading System cannot function without it.
This Process determines the current Trading System Time
That time is used by Server and Client Processes alike.
This Process Reads The Database.
It can only function if the Sybase Service Is Active
Its task is to provide generic data enquiries based on the message recording tables.
If this Process is not functioning the Back Office Interface Client cannot retrieve
trades and trade related information for transmission to TMS/C21
If the Price Reporting System Interface Client fails, it too depends on ATS for a successful restart.
This Process Reads The Database.
It can only function if the Sybase Service Is Active
Its task is to read the prices and limits for each contract and download them to each connected client,
This Process write to a text file the trades and allocations generated using the Trading System
Due to the high coupling of ATS, BOInterface and TMS this Process is essentially a fallback plan
for any of those programs failing.
This is not really a Server Process
The Servers do depend on the database being up during start-up
but after it is not mandatory.
This is not really a Server Process
It is more a record to indicate that replication should be suspended during the day data translation phase
This Process used to handle the market timer updates
The functionality has now been moved to the Central Matching Engine.
This Process has been deprecated.
It used to be the case that clients would connect to RB Server
and a few of these Servers would connect to Central Server.
It is the general practice that the source code is extracted from Microsoft Visual Source Safe
to the directory u:\src [actually export/home/user/src in the proper unix terms] via a build machine.
There are two major working script routines
In the case of make this is a complier program that expects to find makefile instructions
make clean ensures all the previous build items are removed
make then creates all the output binaries
The made.ksh script copies the entire build, binaries and source to an export location
It is the responsibility of the Unix Administrators to copy these files from the developer environment
to the production environment
The detailed how to create servers and clients can be found in the build document.
| |
|
|
|