Try TT Now

SGX Migration Client Impact

What is the X_TRADER® Impact?

 

Can I migrate existing workspaces?

Yes. Since price series keys are not changing, existing workspaces may be used.

How do I manage working orders during migration?

Prior to migration, traders must cancel all working orders, including GTC, GTD, and GTDate orders entered for SGX products.

Will spreads in Autospreader that include SGX products have to be deleted in advance of the migration and rebuilt after migration?

No. Since price series keys are not changing, existing spreads may be used.

Are Wholesale Orders supported?

No. Note that as of September 19th, 2016, SGX has migrated OTC functionality to the SGX Titan OTC API. Customers who wish to place wholesale trades via X_TRADER must provision a TT SGX_OTC Gateway.

What is the impact to X_TRADER® Plug-ins?

 

Is there impact to RTD?

No.

What is the impact to Trade Tracker or other X_TRADER® Professional Services

None

What is the X_RISK Impact?

 

Can I migrate existing workspaces?

Yes. Since price series keys are not changing, existing workspaces may be used.

What if I currently use an X_RISK Historical Fill Server (HFS)?

You can begin recording data from the new SGX Gateway following the migration.

Will SODs be carried over or do I have to publish via X_RISK?

If installing a new SGX Gateway, TT recommends closing all trader positions on the existing SGX Gateway before migrating to the new SGX Gateway. Users must manually enter SOD records for any outstanding SGX positions.

How Do I Migrate Traders in TT User Setup?

 

Can traders use their existing trader IDs on the new SGX Gateway?

SGX is issuing new sessions to customers for use on the Titan API. Customers must create new gateways logins, or modify existing logins as necessary.

Customers should create new SGX-specific order sessions. New, SGX-specific order sessions may be added to the SGX Gateway as described in the SGX Gateway Help at: https://www.tradingtechnologies.com/help/sgx-gateway/configuring-the-order-server/understanding-order-management/.

Updates to Customer Defaults should be completed following the migration, (e.g., updating Account Types if necessary).

Single Broker TTNET Client

Follow the steps below for each of the existing GW flavors by using migration tool in TTUS.

Step Summary:

  • Advanced Prep - Create new flavors by copying from existing for the Go-Live weekend
  • On or after November 11th - Enable new flavors and disable old flavors. Update “Connection” in Customer Defaults if it is used.
  • Post Go-Live - Delete existing (old) flavors from TTUS after the exchange announces the final decision for go-live
 

To migrate users to the new Gateway:

  1. Create new flavors by copying from existing prior to the go-live on November 14th.
    • Prior to the go-live, go to Server Admin > Migrate Users to New Gateway.

    • Uncheck “Delete Gateway Logins related to source gateway” to leave existing (old) flavors, and use “Set all to unavailable (unchecked)” and “Set all to manual (unchecked)”.

    For the description of each parameters, refer to https://www.tradingtechnologies.com/help/tt-user-setup/server-administration/migrating-users-to-a-new-gateway/

    sgx-ttus1
  1. Disable old flavors and enable new flavors <

    After the close on November 11th, disable the old Gateway flavors and enable the new flavors from User Admin > User’s Gateway Login Attributes > Filter on a flavor > Select All Rows > Edit.

     
    • Filter on the old GW flavors and disable: Uncheck “Available to User” “Available to FIX Client” “Automatically Login” and Save.
    • Filter on the new GW flavors and enable: Check “Available to User” “Available to FIX Client” “Automatically Login” and Save
    sgx-ttus2

    The step above covers Gateway Login, Gateway Login Product Limit, Account Based Product Limit, and Customer Defaults, except for the “Connection” field in Customer Defaults. The “Connection” field has to be updated manually. To find out if “Connection” is configured, go to User Admin > X_TRADER Customer Defaults, and ensure “Conn Gateway” and other  “Conn xxxx” fields are empty.

    sgx-ttus3  
  1. Delete existing (old) flavors from TTUS after the exchange announces the final decision for go-live.
 

ASP (MultiBroker) Client

The step are the same as above for Single Broker TTNET, except that migration of the existing GW flavors to the new GW flavors will be handled by TT. Refer to the above for details.

 

Step Summary:

          1. After close of trading on October 28th - Enable new flavors and disable old flavors. Update “Connection” in Customer Defaults if it is used.
          2. Post Go-Live - Delete existing (old) flavors from TTUS after the exchange announces the final decision for go-live.
 

How do I migrate product limits under Gateway Login?

The Migrate Users to New Gateways steps will migrate all Product Limits copied to the new flavor.

For adding/editing Product Limit, refer to the following Help. https://www.tradingtechnologies.com/help/tt-user-setup/gateway-login-risk-administration/creating-product-limits-for-gateway-logins/

What is the impact to API Applications?

 

Are there changes to various API fields?

The following tags will not be changing, and no major impact is expected for API applications:

          • LongSeriesName
          • Series Key
          • Product Code
          • Expiry
 

Customers are encouraged to perform testing prior to the launch to ensure that no other tags have changed which might impact their applications.

 

What is the impact to SGX products?

None.

What is the minimum version of TTAPI/X_TRADER API?

There are no dependencies that are version specific due to the upgrade to the new SGX platform.

How does this migration impact existing FIX Adapter users?

Prior to migration, traders must cancel all working orders, including GTC, GTD, and GTDate orders entered for SGX products. The exchange will not migrate any working orders to Titan.

Customers should adjust TTChron on FIX Adapters to correctly handle the new exchange schedule:

sgx-exchange-times

What is the FIX Client Impact?

The following tags will not be changing, and no major impact is expected for FIX Adapter:

          • LongSeriesName
          • Series Key
          • Product Code
          • Expiry

Customers are encouraged to perform testing prior to the launch to ensure that no other tags have changed which might impact their applications.

Is there impact to FIX Adapter logins in TT User Setup?

You must update all FIX Adapter Client and Server Gateway Logins with correct logins as necessary. SGX is issuing all new sessions to customers for use on the Titan API, so new gateway logins are required.

Can I migrate existing trader positions?

 

How do I handle Position Management during migration?

Customers must delete all working orders prior to the uninstall and reinstall of the SGX 7.18 gateway. Positions for SGX products will not persist to the new SGX Gateway. TT recommends closing all trader positions on the existing SGX Gateway before migrating to the new SGX Gateway. Users must manually enter SOD records for any outstanding SGX positions.

Note: Pre-migration fills will not be retrieved from the old SGX Gateway. After the migration, new *bof.tbl and *fills.tbl files will be created.

Can I use Auto-SOD with the SGX Gateway?

If Auto-Calculate-SOD was enabled on the existing SGX Gateway, ensure that it is enabled on new SGX Gateway after installation. As long as the Fill Server rollover times are the same for all products traded on the SGX Gateway, you can use the Auto-Calculate-SOD functionality after the migration.

Due to changes in the exchange’s trading hours, the new SGX Gateway uses a different fill server rollover time than the old SGX Gateway. The fill server rollover currently occurs at 3:00am Singapore Time, but will change to 4:50am on the new SGX Gateway.

Can GTC, GTD, and GTDate orders remain working in the market during the migration?

WARNING: As part of the migration, SGX traders must delete all working orders and resubmit them on the newly installed SGX Gateway. This includes all synthetic and native orders submitted for SGX contracts on Synthetic Strategy Engine and Autospreader® Strategy Engine servers.

At the end of the trading session prior to migration, traders must cancel all GTC, GTD, and GTDate orders that were submitted on the old SGX Gateway.

WARNING: The exchange will not migrate any orders to the new platform.

After the migration is complete, do the following:

          • Start the SGX Gateway prior to the first trading session in order to download settlement prices from the exchange.
          • Have traders connected to the SGX Gateway resubmit their GTC, GTD, and GTDate orders for SGX products.
          • For SGX Gateways connected to Strategy Engines, have traders resubmit their GTC, GTD, and GTDate spread orders to the Autospreader SE and synthetic orders to the Synthetic SE for SGX products.

What is the FMDS Impact?

 

What configuration changes are required to FMDS?

None. Neither product names nor series keys are changing as a result of this migration.

What is the recommended FMDS Version?

TT recommends users upgrade to FMDS Version 7.6.1 or higher.

What is the TT Gateway Impact?

 

How do I configure the Order Server:

Please refer to the SGX Gateway help.  

How do I configure the Price Server?

The SGX 7.18.Gateway requires a combination of the ITCH and OM price feeds to deliver market data. These feeds are utilized as follows:

 
  • Price Server: The ITCH API is used to deliver streaming, real time price data.
  • Price Bridge: The OM API requires a Market Information ID, similar to previous versions of the SGX Gateway, which is used to deliver certain reference prices such as Settlement and Open/Close.
 
Price Server:

The Price Server uses multicast to deliver streaming, real time price data. Price Server configuration is as follows in the hostinfo.cfg file:

Example

## PRICE SERVER CONFIGURATION ##

[PriceServer]

MulticastGroup=SGX-1

MulticastGroup=SGX-2

 

When configuring Price Server failover, the following should be considered:

  • The secondary SGX Gateway and Price Server must be the same version and configured with the same Exchange-Flavor and multicast channels as the primary SGX Gateway.
  • Any changes made in the aconfig.xml and aconfig_local.mxl files (e.g., enabling PFX) need to be made on both SGX Gateways.
  • The hostinfo.cfg file on both the primary and secondary SGX Gateways must be configured with the following:
    • The same settings for the [PriceServer] section parameters.
    • Identical product subscriptions. For example, if the primary Gateway is subscribing to MulticastGroup=SGX-1, the secondary Gateway must be subscribed to that as well.
  • To configure the secondary SGX Gateway so that only the Price Server runs, comment out the Order Server and Fill Server sections in the ttchron.ini file on the secondary SGX Gateway.
  • Identical MulticastGroups.cfg files are required on both the primary and secondary SGX Gateways.
 
OMPriceBridge:

Each Price Server requires that a Price Bridge is configured using a unique OM Price ID on the host in order to receive Settlements Open/Close and Price Limit prices.

NOTE: The Price Server will fully start up and appear as green in Guardian even without a Price Bridge configured but will not receive Settlements, Open/Close or Price Limit prices.

Price Bridge configuration is as follows in the hostinfo.cfg file:

Example

## PRICE BRIDGE CONFIGURATION ##

[TTP]

UserId=<OM Price ID>

UserPassword=<Password>

AccessIP=<Primary IP Address>

AccessPort=<Primary Port>

AccessIPSecondary=<Secondary IP Address>

AccessPortSecondary=<Secondary Port>

 

Options for configuration of the Price Server and Price Bridge for failover purposes are as follows:

 
  1. In order to support hot failover of the Price Server, each should have a Price Bridge configured with a unique Market Information ID in the hostinfo.cfg.
  2. If customers do not wish to run the Price Server in hot failover mode, the primary Price Server may be configured as follows:
    1. Configure the Price Bridge with an OM Price ID on the primary Price Server
    2. Configure the Price Bridge on the secondary Price Server using the same OM Price ID as the primary Price Server, but comment out the Price Bridge section in TTChron on the secondary server. In this case, should failover to the secondary Price Server occur, Settlements, Open/Close and Price Limit prices will be missing on the secondary. When this occurs, the customer may perform a manual failover of the Price Bridge by enabling it in in TTChron after disabling it on the primary.
 

Price Server Configuration in a SGX Disaster Recovery (DR) Scenario

Since ITCH is not currently supported outside of the SGX colo facility, TT has added the ability for the gateway to run an OM Price Server in the event of a Disaster Recovery scenario.

In order to run the gateway using the OM Price Server, customers should take the following actions:

  1. Stop TTChron
  2. Stop Price, Order and Fill servers
  3. Modify TTChron as follows:

    #[win32-svc-<EXCHANGE_FLAVOR>PriceServer]

    # TO DO: Configure as appropriate for this market and the server time zone.

    #run_days=12345

    #start_time=7:00

    #end_time=2:35

    #days_in_cycle=1

    #tags=<EXCHANGE_FLAVOR>

     

    #[win32-svc-<EXCHANGE_FLAVOR>OMPriceBridge]

    # TO DO: Configure as appropriate for this market and the server time zone.

    #run_days=12345

    #start_time=7:00

    #end_time=2:35

    #days_in_cycle=1

    #tags=<EXCHANGE_FLAVOR>

     

    [win32-svc-<EXCHANGE_FLAVOR>PriceServerOM]

    ## TO DO: Configure as appropriate for this market and the server time zone.

    run_days=12345

    start_time=7:00

    end_time=2:35

    days_in_cycle=1

    tags=<EXCHANGE_FLAVOR>

  4. Start TTChron
 

Note that no configuration changes are required in the hostinfo.cfg file, since the OM Price Server will use the same credentials and configuration as the OMPriceBridge.

 

How do I migrate an existing SGX Gateway to a new SGX Gateway on the same machine?

Upgrades from the TT SGX 7.17.x Gateways to 7.18 are not supported.

Prior to migration, traders must cancel all working orders, including GTC, GTD, and GTDate orders entered for SGX products. The exchange will not migrate any working orders to Titan.

What is the Impact to Algo Design Lab (ADL)?

What is the impact to existing algo templates?

None.

Does this affect ‘persisted’ algo templates?

No.

What is the impact to Strategy Engines (SEs) connected to the new SGX Gateway?

 

What SEs are impacted?

Autospreader® SE, Algo SE, and Synthetic SE servers connected to SGX Gateways in your trading environment are impacted.

 

Do I have to make configuration changes to the SE servers?

No configuration changes for Synthetic SE will be needed unless the gateway flavor will change as a result of the API upgrade.

 

What about working orders on SEs for SGX contracts?

Prior to migrating to the new SGX Gateway, traders must delete all working native and synthetic orders submitted for SGX contracts on a Synthetic Strategy Engine, Algo SE, or Autospreader® Strategy Engine server.