AlgoTraderAlgoTrader Documentation

Quick Start Guide


The AlgoTrader Quick Start Guide is based on the AlgoTrader 30-day trial provided via Amazon AWS which can be requested here.

The AlgoTrader 30-day trial version includes a fully functional AlgoTrader installation as well as the following example strategies:

The AlgoTrader 30-day trial version contains the following pre-installed components:

  • Java JDK

  • AlgoTrader Server

  • AlgoTrader Eclipse IDE

  • MySql Database

  • InfluxDB Database

  • Toad for MySql Freeware

  • InteractiveBrokers Gateway

  • Tortoise Git

  • Git for Windows

  • Notepad++

  • Google Chrome

  • MS Excel (not activated)


Amazon AWS usage cost will apply based on the instance type select. For further details, please visit


It is prohibited to reverse engineer, decompile, disassemble, or copy any parts of the AlgoTrader 30-day trial

The following steps will guide through the installation of a Windows AWS Instance containing the AlgoTrader 30-day trial version

  1. Open the Amazon AWS console:

    and Login using the Amazon username and password.

  2. In the upper right-hand corner of the screen make sure the N. Virginia Region is selected:

  3. Select EC2

  4. Click Launch Instance in the middle of the screen

  5. In the menu on the left-hand side select My AMIs and check Shared with me

  6. Select the AlgoTrader-x.x.x-Trial-WIN-xxxx.xx.xx


    The AlgoTrader-x.x.x-Trial-WIN-xxxx.xx.xx image is only available in the N. Virginia Region but not in any other Regions. It is thus necessary that the N. Virginia Region is selected in the top-right corner of the screen

  7. On the next screen select the Instance Type. We recommend at least instance type t2.medium, ideally instance type m5.large


    Amazon AWS usage cost depends on the instance type selected. For further details, please visit:

  8. Click Review and Launch on the bottom right of the screen

  9. Click Launch on the bottom right of the screen

  10. On the Dialog that shows select Proceed without a key pair, select I acknowledge... and click Launch Instance

  11. Click View Instances on the bottom right of the screen

  12. On the next screen, you can see the Instance starting up. Wait until it is running and note the Public IP address.


    It will take at least 4 minutes for the Instance to startup and become available.

  13. Use Microsoft Remote Desktop to connect to the instance by typing in the Public IP address that was noted in the previous step


    • You need to use Remote Desktop Connection (RDP), a Web Browser will NOT work for this

    • For more information on Remote Desktop Connections please visit: Windows, Mac and Linux

  14. Specify User name and Password that was provided in the Email after signing up for the AlgoTrader free 30-day trial.

  15. On the next dialog select Don't ask... and click Yes

  16. Microsoft Excel is pre-installed on the machine to view the AlgoTrader Excel based Back Test Report. However due to licensing restrictions Microsoft Excel has not been activated yet. If a Microsoft Office license is available, please active Microsoft Excel using the license key. Alternatively, one can request a free 60-day trial through:

  17. Copy the license key that was provided in the Email after signing up for the AlgoTrader free 30-day trial into the file /algotrader-conf/src/main/resources/

  18. The Amazon Instance including AlgoTrader is now ready for usage!


  • Amazon Windows Instances tend to run a bit slow when they are first created. Responsiveness will however increase after some time.

  • The performance of the Amazon Instance also depends on the instance type selected in step 7.

This section gives a quick introduction on how to start a trading strategy by discussing the Box example strategy.

To start any of the other strategies please consult the relevant parts in the documentation:

First one needs to start the AlgoTrader Eclipse IDE (Integrated Development Environment) using the Eclipse icon in the task bar.

The back-test in this example strategy runs with CSV files. If you have a historical data provider that AlgoTrader supports, you could also run vs. InfluxDB and would have to load the historical data first by running a HistoricalDataStarter (see Historical Data).

Launch the SimulationStarter-simulate-box by first clicking the downward facing arrow next to the green start icon.

The system will now perform a back test based on historical data

Once the back test has finished, the Excel based back test report will open automatically.

For further information regarding back testing, visit the following chapters in the documentation:


In case the console shows an error message like "Address already in use" this means that there is already an instance of AlgoTrader running. Please check the list of currently running process and stop the existing AlgoTrader instances before starting a new one.

The following sections describes how to use AlgoTrader in Live Trading mode by using Interactive Brokers for market data and trading.

Before starting the strategy in live trading mode, the Interactive Brokers Gateway needs to be started using the API icon in the task bar.

Then select IB API, enter the Interactive Brokers username and password and select Paper Trading:

Once the Interactive Broker Gateway has started, go to Configure / Settings, then select API / Settings, make sure that Read-Only API is disabled and Socket port is set to 4001.

Now launch the EmbeddedStrategyStarter-box by first clicking the downward facing arrow next to the green start icon. This will start the AlgoTrader server as well as the Box strategy and will connect to the InteractiveBrokers Gateway.

Once the system is started up it will automatically open the HTML5 front-end (within the Chrome browser).


In case the frame on the right side of the screen named Box Strategy does not show up, please click Shift + Reload

For further information on live trading, please visit Starting a Strategy in Live Trading Mode

For further information on the AlgoTrader Web Front-end please visit the AlgoTrader documentation regarding the HTML5 client

This section will give a quick introduction on how to create a trading strategy by discussing the EMA (Exponential Moving Average) Strategy


The AlgoTrader 30-day free trial already contains the final EMA strategy with all artifacts. In case you want to follow below steps please delete the existing EMA strategy first.

The Strategy Wizard also generated boiler plate code that needs to be replaced with the actual logic of the EMA strategy.

AlgoTrader strategies are regular Java programs. Due to this any type of java library or add-ons can be used. The EMA strategy is based on the TA4J library which contains a collection of over 100 technical indicators.

Now, double click the file which contains the main logic of the EMA strategy.

The header of the is already generated and no further changes are necessary. It contains the java class name (EMAService) as well as the name of the interface it is derived from (StrategyService). Also, it contains an @Component annotation which marks the Java class as a Spring bean and automatically gets references to necessary service like the OrderService and the LookupService.


For Spring Auto-Wiring to work the package name needs to be ch.algotrader.strategy. If a different package is assigned services (e.g. OrderService and LookupService) will not be available.


public class EMAService extends StrategyService {

The next part of the contains settings the strategy will use. Three of them are already generated by the Wizard but a few more need to be added.

private final long accountId = 204;
private final long securityId = 860;
private final BigDecimal orderQuantity = new BigDecimal("0.002");
private final int emaPeriodShort = 10;
private final int emaPeriodLong = 20;
private final String defaultFeedType = "BNC";
private TimeSeries series;
private DifferenceIndicator emaDifference;
  • The accountId defines the id of the account the strategy will use for trading.

  • The securityId will define the id of the instrument the strategy will trade.

  • The orderQuantity is the number of contracts the strategy will trade.

  • The emaPeriodSort is the look back period of the shorter EMA indicator.

  • The emaPeriodLong is the look back period of the longer EMA indicator.

  • The defaultFeedType indicates we want to get market data from Binance by default.

In addition, the following two fields need to be defined:

  • The TimeSeries object used by the exponential moving average indicators

  • The DifferenceIndicator which will contain the difference between the short and the long EMA

Next, the Java Constructor for the EMAService class needs to be created:

public EMAService() {

        this.series = new BaseTimeSeries();
        ClosePriceIndicator closePriceIndicator = new ClosePriceIndicator(this.series);
        EMAIndicator emaShort = new EMAIndicator(closePriceIndicator, this.emaPeriodShort);
        EMAIndicator emaLong = new EMAIndicator(closePriceIndicator, this.emaPeriodLong);
        this.emaDifference = new DifferenceIndicator(emaShort, emaLong);
  • First the EMAService constructor sets the name of the Strategy used during the back test.

  • Next the TimeSeries object is initialized to a length of one Bar. In addition, the number of bars the Time Series is set (in this case 20 Bars).

  • Next a ClosePriceIndicator is created which causes the system to look at closing prices of Bar events.

  • Then both the short and the long EMA indicator need to be created by associating them with the ClosePriceIndicator and setting the lookbackPeriod (in this case 10 and 20).

  • Last the DifferenceIndicator needs to be created which contains the difference between the sort EMA and the long EMA indicator.

Next, update the onStart (an AlgoTrader Live Cycle Method) method, which will be called when the strategy starts up.


public void onStart(final LifecycleEventVO event) {
    getSubscriptionService().subscribeMarketDataEvent(getStrategyName(), this.securityId, defaultFeedType);

For further details please visit the AlgoTrader documentation regarding Life Cycle Events.

The onStart methods calls subscribeMarketDataEvent of the SubscriptionService by passing the strategyName and the securityId of the instrument the strategy wants to receive market data for. The SubscriptionService is automatically made available to the strategy through Spring Auto Wiring.

Next, update the onBar method, which will be invoked on every incoming Bar:


public void onBar(BarVO bar) {
    int i = this.series.getEndIndex();
    Decimal currentValue = this.emaDifference.getValue(i);
    Decimal previousValue = this.emaDifference.getValue(- 1);
    if (currentValue.isPositive() && previousValue.isNegativeOrZero()) {
    } else if (currentValue.isNegative() && previousValue.isPositiveOrZero()) {
  • The method first calls the addTick method which will add the incoming Bar to the Time Series defined above

  • Next, the index i of the last element of the Time Series is retrieved

  • Then the value of the last and the second-last element of the DifferenceIndicator is retrieved

Then the actual trading rules need to be defined:

  • If the current value of the DifferenceIndicator is positive and the previous value was negative or zero a BUY order is sent. In other words, if the short EMA crossed above the long EMA a BUY order is sent.

  • If the current value of the DifferenceIndicator is negative and the previous value was positive or zero a SELL order is sent. In other words, if the short EMA crossed below the long EMA a SELL order is sent.

The trading logic is depicted in the following chart also.

As the last item, create the sendOrder method, which will take care of constructing an order object and handing it over to the OrderService:

private void sendOrder(Side side) {

    MarketOrderVO order = MarketOrderVOBuilder.create()

The sendOrder method creates a MarketOrder by using the MarketOrderVOBuilder and assigns the strategyId, the accountId, the securityId, the orderQuantity, the order side (BUY or SELL) and finally calls build to create the MarketOrder object. The order object is then handed over to the OrderService which will execute the order. The OrderService is automatically made available to the strategy through Spring Auto Wiring.

For further details on how order are please visit the AlgoTrader documentation regarding Order Management

In addition the following Java import statements need to be added to the top:

import org.ta4j.core.BaseTimeSeries;
import org.ta4j.core.Decimal;
import org.ta4j.core.TimeSeries;
import org.ta4j.core.indicators.EMAIndicator;
import org.ta4j.core.indicators.helpers.ClosePriceIndicator;
import org.ta4j.core.indicators.helpers.DifferenceIndicator;
import static ch.algotrader.util.TA4JUtil.toTick;

The implementation of the trading strategy is now finished a first back test can be started according to Chapter 3, Starting a Trading Strategy.

The EMA strategy is an example strategy based on Java code only. For details on how to build a trading strategy using Esper please visit the AlgoTrader documentation regarding Strategy Development

During live trading, all relevant information like orders, positions and transactions are stored in the MySql database.

To view database data please open TOAD for MySql.

On the left-hand side of the application double click on root@localhost (algotrader).

You now see all AlgoTrader tables listed below

To view the contents of a table (e.g. the strategy table), double-click its name and go to the Data tab

The table security contains a list of all available instruments that can be traded with the system. This table can for example be used to find the securityId for the BTC/USDT pair traded on Binance.

The AlgoTrader 30-day trial version can also be used to trade Bitcoin and other Cryptocurrencies via the following exchange adapters:

This chapter describes how to setup trading with the Binance exchange.

To setup a connection to Binance the following steps have to be taken:

  • Sign-up for a Binance account on Register with Binance

  • Enable two factor authentication (2FA) on the account following the 2FA instructions (either SMS or Google Authenticator) on the Account Page

  • On the account page generate a new Binance API key and Secret Key and use it in the settings below.

First the Binance API key, then the Secret Key noted above need to be added by clicking the downward facing arrow next to the green start icon and then selecting Run Configurations.

In this example we are going to use the existing EMA strategy to trade via Binance. For this purpose the Binance API key and Secret Key need to be added to the Eclipse launch configuration EmbeddedStrategyStarter-ema-binance by selecting it on the left-hand side and going to the Arguments Tab

Here the Binance API key and Secret Key noted above need to be added. Then click Apply.

Per default the EMA strategy trades the EUR/USD currency pair through Interactive Brokers. To now switch the strategy to trade through Binance we need to update the settings at the top of the EMAService:

  • Update the accountId to match the Binance account in the database.

  • Update the securityId (securityId 860 represents the BTC/USDT cryptocurrency pair on Binance).

  • Update the orderQuantity to a small enough number

  • Update the defaultFeedType BNC in order for the strategy to subscribe for market data through the Binance adapter.

  • Update the order quantity in the SendOrder method to match the new data type set above.

Now the strategy can be started by selecting the EmbeddedStrategyStarter-ema-binance and click Run.

You can shut down the system by clicking on the Start Menu in the lower left-hand corner of the Windows Desktop and then select Power Options in the upper right-hand corner:

Alternatively, the system can be shutdown via the Amazon AWS Console by first selecting the Amazon Instance and the under Actions select Instance State and then either Stop or Terminate


  • If Stop is clicked the instance can be restarted at a later point in time. In the stopped state the Amazon Instance will still incur disc space using costs as mentioned in:

  • If Terminate is clicked the instance cannot be restarted. In the terminated state, no further Amazon instance costs apply