Support Board
Support Board
Search Board
Control Panel
View My Posts / Threads
Direct MessagesDate/Time: Sat, 04 May 2024 10:13:11 +0000
Post From: Introduction to DTC Server and Multiple Sierra Chart Instances
| [2016-03-19 18:21:56] |
| |
|
We have completed the development of the DTC Server in Sierra Chart. There still is some more testing we are doing. However, at this point in time it is considered complete and ready for use for real-time market data, historical price data, and trading. We will be adding to our documentation and maybe making a video or two for this capability. This is the current documentation: https://www.sierrachart.com/index.php?page=doc/doc_DTCServer.php#UsingDTCServerForDataAndTradingInAnotherSCInstance Basically it allows the market data and trading functionality in one instance of Sierra Chart to be shared with others. This can be on the same computer or across the Internet. So you are now able to share the external market data or trading connections with other instances of Sierra Chart. Information about the DTC protocol can be found here: http://dtcprotocol.org/ One use of this would be to run Sierra Chart on a server with reliable connectivity and share the connection with other instances of Sierra Chart. For trading, this effectively creates server-side OCO and bracket order functionality. So you can create this capability for Trading services that do not support this or do not do it very reliably. Another advantage is that the instance of Sierra Chart which is connected directly to the main trading service will maintain long-term order fill history, dependent on Global Settings >> General Trade Settings >> Number of Days to Save in Trade Activity Log, and that order fill history can be shared with other instances of Sierra Chart so you have consistent order fill history among instances of Sierra Chart. This is the kind of configuration which we use for LMAX and FXCM. Although the particular version of Sierra Chart that runs on a server is programmed to handle multiple user authentication and maintains a logical separation between trading accounts. The communication protocol used is an open specification protocol meant for adoption by the industry. Therefore, you can see the advantages of the DTC Server and Client functionality we have developed and the use of a well-designed communication protocol. ---- Sierra Chart version 1383 is now available. You need to update to the latest prerelease for this. Here are instructions: https://www.sierrachart.com/index.php?page=doc/download.php#FastUpdate There is a new command available: File >> New Instance. This command will start a new instance of Sierra Chart in a subfolder named SierraChartInstance_#. Where the # is the instance number. This is a completely separate and independent running instance of Sierra Chart which connects to the primary instance through the DTC Server to receive market data and to support trading. Simulated trading will still be handled within the running instance itself and not use the DTC server. Although if the primary instance has Trade Simulation Mode enabled and one of the sub instances that has been started has Trade Simulation Mode disabled, then Orders submitted from this sub instance will be simulated in the primary instance. This instance of Sierra Chart has its own data files, configuration files and Chartbooks. It runs as a completely separate process and can be moved to any monitor if you have multiple monitors. Sierra Chart Support - Engineering Level Your definitive source for support. Other responses are from users. Try to keep your questions brief and to the point. Be aware of support policy: https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation For the most reliable, advanced, and zero cost futures order routing, *change* to the Teton service: Sierra Chart Teton Futures Order Routing Date Time Of Last Edit: 2016-03-19 23:39:17
|