Planning an OSE Migration
Before You BeginUse this page to plan a migration of users of OSE Gateways due to the Osaka Exchange (OSE) Next Generation Derivatives Trading System (Next J-GATE) upgrade, which includes a new ITCH price feed in addition to the OM API changes.
What are the major changes introduced by the API upgrade?The API upgrade changes the following for OSE Gateway users:
- Introduces New OSE products: Tokyo Stock Exchange Mothers Index Futures, JPX-Nikkei Index 400 Options, TWSE Capitalization Weighted Stock Index Futures, and FTSE China 50 Futures
- Moves the end of the Night Session from 3:00 a.m. to 5:30 a.m.
- Moves up the start of the Day Session from 9:00 a.m. to 8:45 a.m. for index futures
- Introduces Non-cancel periods (NCP) for Nikkei 225 Futures, Nikkei 225 mini, TOPIX Futures(Large contract), during which order amendments/cancellation are not accepted
- Deprecates support for Native Stop orders: Customers must now utilize Synthetic Strategy Engine (SSE) for Stop Order functionality
When should I migrate?OSE will conduct the Next J-GATE upgrade on Tuesday, July 19, 2016. The TT OSE Gateway must be upgraded after the close of trading on Friday, July 15, 2016. The migration is done once, and it should be done at a time that is best for your particular trading environment. However, TT recommends that you perform this migration during non-trading hours. Ideally, you should begin these steps following the close of the last trading day prior to migration and complete them over the course of the subsequent weekend.
What testing is required by the exchange, and what are the required test dates?For the most part, Next Generation J-GATE Conformance Testing of Trading Technologies (TT) software will be completed internally by TT engineers. For system failure tests, however, the participation of TT customers is required. All tests must be completed in the Production Environment using Login IDs provided by the exchange to the test participant.
What are differences between new OSE gateways due to the API upgrades?Differences include:
- The new TT OSE Gateway requires a 64 Bit Operating System, for example Windows Server 2008, 64-Bit.
- TTChron changes to support OSE’s extended trading hours as follows:
- Day Session of Index Futures will begin at 8:45 AM
- Night Session will be extended to 5:30 AM
- OSE is introducing a Night Session for the Nikkei VI Futures from 16:30 to 19:00
- TT Gateways will initialize at 7 AM and shutdown will be 6 AM
How do I prepare my TT Trading Environment?
Can I upgrade an existing OSE Gateway?No. A clean install, or uninstall/reinstall is required since the architecture is moving from 32 to 64 bit. Prior to migration, traders must cancel all working orders, including GTC, GTD, and GTDate orders entered for OSE products.
What version of the OSE Gateway should I use?All users should migrate to OSE Gateway 7.18, which is currently available through your TAM. For information on installing and configuring a OSE Gateway, refer to the OSE Gateway System Administration online help.
What are the minimum supported versions of TT Client applications?Currently, there are no expected client version dependencies associated with the OSE 7.18 Gateway. Trading Technologies will notify customers, as well as update this document, should any additional dependencies be determined.
What is the Licensing and Billing Impact?
Can I reuse my current OSE Gateway licenses?Customers will be provided with a free gateway license for use during conformance and exchange testing prior to the launch of the new API. This test license must be requested by customers via the normal process, and they must also request a cancellation of this license prior to the launch in order to avoid being billed. For a description of TT licensing, refer to TT Gateway Architecture System Administration.
Canceling OSE LicensesDuring the conformance testing period, TT is offering customers OSE Gateway licenses for temporary gateways used for conformance purposes free of charge. These licenses will become billable once the exchange goes live on the NEXT J-Gate platform. Customers must submit license cancellations via the TT Website for TT OSE Gateways that are no longer in use following the migration. TT will not automatically cancel any licenses.
X_TRADER® and X_RISK® LicensesX_TRADER® and X_RISK® licenses are market-based. As part of the migration, users are required to verify that the OSE market appears in their X_TRADER® and X_RISK® licenses in order to log in to the OSE Gateway.
Billing Server ImpactThere is no impact on the TT Transaction Billing Server. After the migration, fills and billing packets will continue to be recorded and transferred daily to the TT Licensing Department Accounting and Billing System and will contain the Exchange ID of the newly installed OSE Gateway. The TT Licensing and Accounting Department will be notified by your TAM that the new gateway is installed and the exchange IDs have changed.
OverviewThe following checklists show the chronological steps for a successful migration to the OSE Gateway.
Pre-Migration ChecklistYou should complete the items below to prepare for migrating gateways.
|Obtain required TT Software licenses||Obtain new OSE Gateway licenses for each new or upgraded gateway. Refer to What is the Licensing and Billing Impact?.|
|Upgrade all client applications||Refer to What are the minimum supported versions of TT Client applications?|
|Prepare X_TRADER® for migration||Delete all working orders from the exchange. Create new workspaces. Refer to What is the X_TRADER® Impact?|
|Prepare X_TRADER® plug-ins for use with the OSE Gateway||Refer to What is the impact to X_TRADER® Plug-ins?|
|Prepare trader logins for migration||Configure new Direct Trader IDs. Configure TTORD Trader IDs. Add any new/additional Trader IDs. Refer to How Do I Migrate Traders in TT User Setup?|
|Prepare trader positions||Enter existing trader positions. If enabled on the current gateway, enable the Auto-Calculate-SOD functionality on the new OSE Gateway. Refer to Can I migrate existing trader positions?|
|Prepare FIX Adapter for migration||Refer to How does this migration impact existing FIX Adapter users?|
|Prepare X_RISK for use with the OSE Gateway||Add OSE Gateway logins Update the Historical Fill Server database Refer to What is the X_RISK Impact?|
|Migrate the existing gateway to a OSE Gateway||Refer to What is the TT Gateway Impact?|
|Check ADL templates||Refer to What is the impact to Algo Design Lab (ADL)|
|Check any Strategy Engines||Refer to What is the impact to Strategy Engines (SEs) connected to the new OSE Gateway?|