← Back to X_TRADER® Help Library

Migration Documentation

eSpeed NFI Migration Client Impact

What is the X_TRADER® Impact?

 

Can I migrate existing workspaces?

Existing workspaces may not be used as the symbols are changing for NFI.

 

How do I manage working orders during migration?

No impact, as GTC orders are not supported in NFI.

 

Are Wholesale Orders supported?

No.

 

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?

 

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

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

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

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

 

How Do I Migrate Traders in TT User Setup?

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

The exchange is issuing new sessions to customers for use on the new eSpeed API. Customers must create new gateway logins using new credentials provided by the exchange.   Customers should create new eSpeed/NFI-specific order sessions. New, eSpeed/NFI-specific order sessions may be added to the eSpeed Gateway.   Updates to Customer Defaults should be completed following the migration, (e.g., updating Account Types if necessary)  

Single-Broker TTNET Client

Follow these steps for each of the existing Gateway flavors by using migration tool in TT User Setup.   Summary instructions:
  1. Advanced Prep - Create new flavors by copying from existing Gateways for the Go-Live weekend.
  2. On or after October 29th - Enable new flavors and disable old flavors. Update the “Connection” values in Customer Defaults if it is used.
  3. Post Go-Live - Delete existing (old) flavors from TT User Setup after the exchange announces the final decision for go-live.
  Detailed Instructions:
  1. Create new flavors by copying from existing prior to the go-live on October 29thPrior 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 parameter, refer to https://www.tradingtechnologies.com/help/tt-user-setup/server-administration/migrating-users-to-a-new-gateway/

The Source,Target and setting information in the screenshot are for example purpose only.

  1. Disable old flavors and enable new flavors
After the close on February 23rd, 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 them by unchecking “Available to User” “Available to FIX Client” and “Automatically Login”.  When this is complete, click Save.   Filter on the new GW flavors and enable them by checking “Available to User”,  “Available to FIX Client”, and “Automatically Login”, When this is complete, click Save. This Step covers Gateway Login, Gateway Login Product Limits, Account Based Product Limits, 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.  
  1. Delete existing (old) flavors from TT User Setup 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.   Summary instructions:
  1. After close of trading on October 29th - 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 TT User Setup after the exchange announces the final decision for go-live.
Detailed instructions: See the previous section.  

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 be changing as part of NFI migration  
  • Series Key
  • Product Code
  • Expiry - (NFI has correct day in addition to Month and Year, eSpeed had only Year and Month)
  The following tags will not be changing as part of this migration
  • LongSeriesName
  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 NFI (eSpeed) products?

The symbols are changing.  

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 CFE platform.  

How does this migration impact existing FIX Adapter users?

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

What is the FIX Client Impact?

The following tags will be changing as part of NFI migration  
  • Series Key
  • Product Code
  • Expiry - (NFI has correct day in addition to Month and Year, eSpeed had only Year and Month)
  The following tags will not be changing as part of this migration  
  • LongSeriesName
  The impact for Fix Adapter needs to be assessed based on the same.   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. The exchange is issuing all new sessions to customers for use on the new eSpeed API, so new gateway logins are required.

 

Can I migrate existing trader positions?

 

How do I handle Position Management during migration?

No Impact as there is no Position migration  

Can I use Auto-SOD with the eSpeed Gateway?

No Impact  

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

GTC and GTD are not supported for NFI

 

What is the FMDS Impact?

 

What configuration changes are required to FMDS?

There will be no impact for TTNET. For locally hosted customers, the rename commands should be used to make the FMDS work properly.  

Rename can be done via file monkey via the commands below or through the FMC data management tab. The naming convention goes (old) espeed.usg_02Y.bond -> (new) espeed.2Y_UST.bond. Please note the missing leading 0 on single digit years.

 

Filemonkey command:

FMDSFileMonkey.exe --rename -c “eSpeed.usg_02Y.Bond” --new-contract “eSpeed.2Y_UST.Bond”

FMDSFileMonkey.exe --rename -c “eSpeed.usg_30Y.Bond” --new-contract “eSpeed.30Y_UST.Bond”

 

What is the recommended FMDS Version?

TT recommends users upgrade to the latest FMDS Version 7.6.4.5p26 for 32bit, 7.6.4.5p29 for 64bit or higher.

 

What is the TT Gateway Impact?

 

How do I configure the Order Server?

  The Hostinfo file which needs to be configured with appropriate production credentials to establish the connection for Orders.   It includes sections for:
  • Exchange credentials such as IP, Port and Password section should be filled with informations received from the exchange.
  • The field “Exchange Company” should be set to “NFI” or can be commented.
  • GatewayCompany field should be filled with “SenderComp” value from the exchange
  • Member field should be filled with TTUS field Direct Trader Member
 

Example - Hostinfo File

 

[location]

Country=

StateProvince=

 

[OrderSession_1]

Member=

ExchangePrimaryIP=

ExchangeBackupIP=

ExchangePort=

ExchangeCompany=

GatewayCompany=

SessionPassword=

 

Order Server

  • The TT eSpeed Gateway Order Server will use the FIX 4.4 protocol for order entry.
  • Self Match Prevention will supported on Exchange side by setting it up based on user preference.
  • There will be change in symbology for the products as the mapping below. The new symbols are mentioned in the first column (NFI)
NFI eSpeed
2Y_UST usg_02Y
5Y_UST usg_05Y
7Y_UST usg_07Y
30Y_UST usg_30Y
10Y_UST usg_10Y
3Y_UST usg_03Y
 
  • The order types supported on X_Trader platform are
    • Limit
    • IOC
    • Reserve
 

How do I configure the Price Server?

  The Hostinfo file must be configured with appropriate production credentials to establish the connection for market data.   The ITCH and GLIMPSE configuration have to be in place to connect to the prices server.  

Example - Price Server configuration in Hostinfo

 

[PriceServer]

MulticastGroup=ESPEED-1

ESPEED-1_ReplayId=

ESPEED-1_ReplayPassword=

logprices=y

 

# Unless your Primary NIC is in the exchange's network,

# uncomment the applicable line(s) below and

# fill in the NIC IP address(es)

NetworkInterface=10.9.20.47

 

Multicast cfg

 

[ESPEED-1]

ChannelNumber=0

Exchange=ESPEED

AddressFeedA=233.56.159.165:18000

AddressFeedB=233.56.159.166:18000

RetransmissionServerA=206.200.9.64:18100

RetransmissionServerB=206.200.9.65:18100

RetransmissionServerGlimpseA=206.200.9.64:18400

RetransmissionServerGlimpseB=206.200.9.65:18400

 

Price Server - Multicast ITCH

  Nasdaq Fixed Income Treasury ITCH is a direct data feed product . The ITCH feed contains data describing all public orders and trades that occur on the Nasdaq Fixed Income (NFI) US Treasury alternative trading system (ATS or System) and features the following data elements:  
  • Reference Data – Order book directory messages provide basic security data such as CUSIP, maturity, and coupon rate.  
  • Event controls – such as start of day, end of day and market holidays  
  • Order level messages – full order book depth is published through a series of order messages to track the lifecycle of each customer order.  
  • Trade messages – trade messages will be used to show traded size for discretion and reserve traded size.
 

Price Server - GLIMPSE

  GLIMPSE is complement to NFI UST ITCH real-time data feed product, GLIMPSE is a point-to-point data feed connection that provides direct data feed customers with a snapshot of the current state of NFI order books. GLIMPSE 3.0 uses the same message formats as NFI-USTs ITCH version 3. GLIMPSE can be used to quickly sync up with the NFI-UST ITCH feed. At the end of the GLIMPSE snapshot it will provide a sequence number that can be used to connect and sync up with the real-time NFI-UST ITCH feed.   GLIMPSE provides the following:
  • Basic Reference Data for each order book including intra-day updates up until the time of login.
  • Current trading state of each order book.
  • All displayable orders for each order book.
  • An End of Snapshot message providing the ITCH sequence number to use.

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

 

What is the impact to existing algo templates?

Algo templates will be changed as Series key is changing for NFI.  

How does this affect ‘persisted’ algo templates?

None.

 

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

 

What SEs are impacted?

None  

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

N/A  

What about working orders on SEs for eSpeed contracts?

N/A