Dear Support,

I need some tips about how to prepare a strategy to able to discover if it is running Local or Remote?
If it runs Local, it has to write data to an output file.
If it runs Remote, it is not possible to write to a file, so the file output functions must be not executed.

I know about IEngine.RunMode(), so technically we should be able to discover the platform type, and allow/disallow the file writing functions.

The problem is that the strategy definition starts with

...
@RequiresFullAccess
public class MyStrategy implements IStrategy {
...

And this @RequiresFullAccess gives troubles under Remote mode.

Is the place of this @RequiresFullAccess line must be the 1st line before the strategy's class definition? Or I could move this line into the onStart() function, and call it after context.getEngine() was called.


Or what else could I do?

As I said, I want the same strategy to be used, no matter where it is running.

One option would be to use JForex SDK
https://www.dukascopy.com/wiki/#JForex_SDK

Strategies can be started remotely with the help of IClient.getRemoteStrategyManager()
Two strategies can be created. One would hold all the functionality.
The other would extend first one and include @RequiresFullAccess annotation.

public StrategyRemote implements IStrategy {}

@RequiresFullAccess
public StrategyLocal extends StrategyRemote  {}

Dear Support,

Thanks for the fast follow-up!

I am not sure if I follow your logic properly, so bare with me a bit more...
Does this mean that two separate strategies will be created?
Remote version, without output creation
Local version, extending the remote version with output creation

This means 2 separate files, one for the remote run and one for locally.


Or rather create a big, 'container' strategy that will be responsible for instantiating the appropriate strategy type (remote, local) upon detecting the engine.RunMode()?

I prefer not to use the SDK to create an application/strategy that will be responsible to start the remote strategy. I would like to have a strategy file, that can be started remotely, or locally, or even in the Historical tester.

If SDK is not used then the easiest way would be to keep 2 separate files - one for remote, one for local run.