Using Multiple Data and Trading Services at the Same Time
- Step-By-Step Instructions to Install Multiple Copies of Sierra Chart
- Accessing Market Data from Other Instances of Sierra Chart
- Using DTC Server for Data and Trading in Another Sierra Chart Instance (Opens in new page)
In this documentation the term "copy" and "instance" have the same meaning. A copy or instance of Sierra Chart is an installation of Sierra Chart in its own folder which runs independent from any other instance or copy.
With Sierra Chart, you are able to run multiple copies/instances of the program at the same time on your computer. The purpose of this is to be able to use more than one different Data or Trading service at the same time. These are the services you select through the Global Settings >> Data/Trade Service Settings >> Service setting.
This can all be accomplished by running multiple copies/instances of Sierra Chart at the same time. Each one is located in its own folder on your computer.
Although it is important to be aware that in the case of when using the Sierra Chart Exchange Data Feed, this data feed can be used on its own and is also integrated with all Trading services. Therefore, there is no need to use multiple copies of Sierra Chart running on your system. You can use just one single copy. For additional information about this, refer to Integration with Trading Services.
There is also the ability to run multiple copies of Sierra Chart using market data and trading functionality from a single Server copy of Sierra Chart. This is very useful because some Data and Trading services only only allow one simultaneous connection per username/account to that particular service.
For additional information about using other copies of Sierra Chart which share the market data and trading functionality from a Server copy of Sierra Chart, refer to Using DTC Server for Data and Trading in Another Sierra Chart Instance.
When using multiple copies of Sierra Chart, each copy of Sierra Chart needs to be located in its own folder on your computer. It is that simple and very reliable.
Before using this feature, it is important to be aware that it is possible in Sierra Chart to use multiple trading accounts within a single copy/instance of Sierra Chart, if the particular Trading service username that you are logged in with, supports multiple trading accounts. For more information, refer to Selecting Trade Account. In this particular case, using multiple copies of Sierra Chart is unnecessary.
Although if the particular Trading service you are using does not support multiple Trade Accounts per username, then using multiple instances of Sierra Chart is necessary, one for each Trade Account.
Step-By-Step Instructions to Install Multiple Copies of Sierra Chart
To use multiple Data or Trading services or Trading accounts at the same time, you need to install additional copies of Sierra Chart. The Sierra Chart licensing allows you to do this. In this way, you will have full access to all the capabilities each service provides.
You can also configure each copy of Sierra Chart to use the same Trading service but a different Trading service account. Multiple copies of Sierra Chart can be run at the same time if each copy is installed to and running from a different folder on your computer. Follow the instructions below to do this:
Installing multiple copies of Sierra Chart is also useful for distributing processing load.
- Download and install a second copy of Sierra Chart to "C:\SierraChart2\" or whatever unused folder you want to use. Download Sierra Chart from the Download page.
- If you want to copy settings from an existing installation of Sierra Chart to a new installation, refer to help topic 15.
- Start the second copy of Sierra Chart in that new installation folder. On your desktop and also from the programs list on the Windows Start menu, you will notice a shortcut icon to the new installed copy of Sierra Chart. The icon name will have the folder you installed Sierra Chart to. You can use that icon to easily start Sierra Chart. You may also want to rename it to a more useful name.
- Login with your same Sierra Chart Account Name and password that you used with the original installation. You can also use another Sierra Chart account if you wish.
- Configure the second copy of Sierra Chart to the Data or Trading Service you want to use it with, by following the setup instructions for the Data or Trading Service you will be using.
- It is essential that every copy of Sierra Chart that you have installed on your system uses a different Global Settings >> General Settings >> Data Files Folder. They cannot use the same Data Files Folder. Otherwise, there will be conflicts, and unusual behavior that we will not provide support for. Verify that each copy of Sierra Chart uses a separate Data Files Folder. Do not pay any attention to any information you may find on the Support Board that mention using the same Data Files Folder. Do not do this. It is no longer supported at all. You are going to create trouble for yourself and for us. By default, each copy of Sierra Chart will use a separate Data Files Folder, so there is nothing special to do in this regard. If you inadvertently or deliberately, used the same data folder, that will corrupt the files in this common data folder, and the chart data files in that folder will have to be deleted.
- By running multiple copies of Sierra Chart at the same time, you can connect to multiple Data or Trading services or service accounts at the same time. You can install as many copies of Sierra Chart as you need. Each one needs to be in its own folder.
- To share data from the data feeds of the multiple copies of Sierra Chart that you have installed and are running, with other copies/instances of Sierra Chart, refer to the Using DTC Server for Data and Trading in Another Sierra Chart Instance page.
- To assign unique names on the title bar of the main window of each instance of Sierra Chart you are running, set this through Global Settings >> General Settings >> General 2 >> Custom Title Bar Name.
Accessing Market Data from Other Instances of Sierra Chart
Sierra Chart supports the ability to access data from various data feeds in a single instance of Sierra Chart. For example, the Sierra Chart Market Statistics Data Feed and the Sierra Chart Exchange Data Feed can be accessed in a single instance of Sierra Chart which is connected to an external Trading service which provides its own market data. This is in order to bring multiple data feeds together into one instance.
However, there are more specialized instances, where you may want to access data from another running instance of Sierra Chart which cannot be directly accessed in a different instance. Follow the instructions below to accomplish this.
This functionality is new as of version 1850 and provides an efficient and standard way to accomplish this with great flexibility.
Applicable to non-Sierra Chart Source Instances As Well
This functionality is also applicable to accessing data from one or more DTC servers which are considered the Source instances, into a Destination instance of Sierra Chart. Whenever the Source instance is referred to in the instructions, in this case this will be considered the DTC server that you provide or have access to, instead of another Source instance of Sierra Chart.
- This documentation will refer to the two instances/copies of Sierra Chart as the Source instance and the Destination instance. The Source instance is where the market data originates from and the Destination instance is where the market data is being accessed or used.
- It is understood that you already have two installed instances of Sierra Chart, each configured to work with the particular Data or Trading service that you want. If this is not already done, follow the instructions in the Step-By-Step Instructions to Install Multiple Copies of Sierra Chart section.
- Run the Source instance of Sierra Chart if it is not already running.
- Select Global Settings >> Data/Trade Service Settings >> SC Server Settings.
- Configure thee settings on that window in the Source instance as shown in the red highlight box here:
- Press OK. Press OK.
- Make sure the Source instance is connected the data feed by selecting File >> Connect to Data Feed. If this command is disabled, then Sierra Chart is already connected. However, an automatic connection will occur anyway when the Destination instance requests data from the Source instance.
- Exit from the Destination instance if it is already running. You can do this with File >> Exit.
- Go to the folder that the Destination instance is installed to on your system. When the Destination instance is running, you can determine its installation folder through the Window >> Message Log. Near the top of the Message Log, the path to the folder will be after Program path:.
- Using a text editor, edit the GlobalSymbolSettings.XML file. This file consists of multiple symbol settings.
- You will need to enter a new symbol settings block like the example below for a symbol that you want to access market data for from in the Source instance. This block of XML data needs to be between the <symbol-settings> </symbol-settings> tags. You can put it anywhere within the file but it needs to be located independently from other <settings> </settings> and not mixed in with another set of settings.
Each set of symbol settings within the Global Symbol Settings file needs to have a unique symbol for each <service-code> </service-code> tag. There cannot be a duplicate symbol for the same <service-code> </service-code> tag. So if you want to access data from a Source instance of Sierra Chart for symbol that is already listed for the current Service you are using in the Destination instance, then edit those symbol settings rather than using a new block of symbol settings.
- The following is the block of symbol settings you need to add. The <service-code> </service-code> tag need to be left blank unless the Symbol Settings already exist for the symbol. This particular tag will be automatically set later by Sierra Chart.
XBTUSD-CUSTOM false BitMEX XBT/USD Perpetual Swap Custom 1 0.5 0.5 false 100 XBTUSD-BMEX 1.0 127.0.0.1:11094 Generic_Sub_Clients 127.0.0.1:11095 SC_DTC_HISTORICAL_DATA_SERVER SC_DTC_HISTORICAL_DATA_SERVER
- The <symbol> tag can be set to any symbol and it can be set to a symbol which is recognized by the data feed of the Destination instance. This symbol can use pattern matching characters and if it does the tag <use-pattern-matching-characters> needs to be set to true. For example, it can be set to a recognized Trading symbol supported in the Destination instance. Or it can be any symbol you want to make up.
- The <source-data-symbol> tag needs to be set to the symbol in the Source instance that you want to map the symbol in the Destination instance to. This symbol can contain pattern matching characters. If pattern matching characters are used, the tag <use-pattern-matching-characters> needs to be set to true. This needs to be set to a symbol which is recognized by the data feed of the Source instance.
- The <source-data-multiplier> tag needs to be set to the multiplier that you want to multiply the Source price data by. Usually this will be set to 1.0.
- The <generic-sub-client-server-address> tag needs to be set to 127.0.0.1:11094. The port number needs to match the port number used by the DTC Protocol Server in the Source instance of Sierra Chart.
- The <realtime-data-client> tag needs to be set to Generic_Sub_Clients.
- The <historical-data-server> tag needs to be set to 127.0.0.1:11095. The port number needs to match the historical data port number used by the DTC Protocol server in the Source instance of Sierra Chart.
- The <historical-daily-data-source> tag needs to be set to SC_DTC_HISTORICAL_DATA_SERVER.
- The <historical-intraday-data-source> tag needs to be set to SC_DTC_HISTORICAL_DATA_SERVER.
- After you are done configuring these different tags, start the Destination instance of Sierra Chart.
- You will see the symbol listed in File >> Find Symbol >> Custom or whatever you have set the <category> tag to. You can then open a chart for it and Sierra Chart will access data for the symbol from the Source instance.
*Last modified Wednesday, 30th January, 2019.