SGX Gateway Documentation
- SGX Gateway And The Exchange
- Installing And Upgrading
- Configuring Global Settings
- Configuring Market Data
- Configuring The Order Server
- Configuration Parameters
- Configuration Parameters: Multi Member
- Disaster Recovery
Trader and Firm Identification
Obtaining Exchange Credentials/Membership
Before trading at SGX, individuals must obtain an SGX Membership. For further details, please refer to the following link:http://www.sgx.com/wps/portal/sgxweb/home/trading/derivatives/membership
TT Direct Trader IDs
You can determine and set up any Member ID, Group ID, and Trader ID you like.
You must complete the following fields in Guardian to map a TTORD proxy trader to a direct trader:
- Exchange: The TT Gateway exchange-flavor (e.g., SGX-A).
- Member: Identifies the client’s Member login.
- Group: A three-digit variable defined by the firm.
- Trader: A multi-digit variable defined by the firm.
TTORD Trader IDs
The following lists how TT SGX Gateways use TTORD trader IDs.
- TT SGX Gateways support TTORDs.
- You can map multiple TTORDs to one direct exchange trader.
Each TTORD ID used to connect to and trade on the Exchange must use a unique clearing account.
FFT2 and FFT3 Fields
By default, SGXs use the FFT2 field to populate the customer_info_s API field. For Give Up orders, it is mapped to ex_customer_s.
In SGX Gateway 7.16 and lower, when using Omnibus account handling, SGXs use the FFT2 field to populate the ex_client_s API field. To enable Omnibus handling, you must set AccountHandling=Omnibus in the hostinfo.cfg file.
SGX Gateways 7.17 and higher do not use the FFT2 field to populate the ex_client_s API field, and AccountHandling=Omnibus is not supported.
For 7.16 and lower, the SGX Risk Controls interface will reject any order submitted with lowercase values in the ex_client_s field. Therefore, users must populate FFT2 with uppercase values when using Omnibus account handling.
For 7.17 and higher, FFT3 can be used for routing omnibus account numbers. If populated, FFT3 is mapped to the ex_client_s API field.
SGXs use the Account field to populate the ex_client_s API field.
The SGX Risk Controls interface will reject any order submitted with lowercase values in the ex_client_s field. Therefore, users must populate Account field in X_TRADER with uppercase values unless they are using Omnibus account handling.
For 7.16 and lower and using Omnibus account handling, SGXs use the Account field to populate the customer_info_s API field. To enable Omnibus handing, you must set the AccountHandling=Omnibus in the hostinfo.cfg file.
For 7.17 or higher, AccountHandling=Omnibus is not supported, so use FFT3 to send an Omnibus account number to the exchange. If FFT3 is populated, the Account field is not sent to the exchange.