|
Standalone API Launch Remote Strategy Execution |
hyperscalper
|
Post subject: Standalone API Launch Remote Strategy Execution |
Post rating: 0
|
Posted: Sun 18 Aug, 2013, 17:13
|
|
User rating: 98
Joined: Mon 23 Jul, 2012, 02:02 Posts: 656 Location: United States, Durham, NC
|
If a .jfx file is present, then I'd like a standalone API feature to launch a Remote Strategy Run at Dukascopy's Remote servers, and to provide startup parameters for each run instance. This would be within the security context of an account sign in, of course, and would work for both Demo and Live accounts.
Thanks, HyperScalper
|
|
|
|
|
hyperscalper
|
Post subject: Re: Standalone API Launch Remote Strategy Execution |
Post rating: 0
|
Posted: Mon 19 Aug, 2013, 15:47
|
|
User rating: 98
Joined: Mon 23 Jul, 2012, 02:02 Posts: 656 Location: United States, Durham, NC
|
I guess it should also be able to stop Remote Strategies, so the question would be what parameters would be needed to enumerate running Remote Strategies, and to identify the correct Strategy to stop.
HyperScalper
|
|
|
|
|
hyperscalper
|
Post subject: Re: Standalone API Launch Remote Strategy Execution |
Post rating: 0
|
Posted: Sat 21 Sep, 2013, 03:21
|
|
User rating: 98
Joined: Mon 23 Jul, 2012, 02:02 Posts: 656 Location: United States, Durham, NC
|
Please let me know when Remote Launch from standalone API will be available.
In the meantime, is there any way to implement the feature in the interim ?
HyperScalper
|
|
|
|
|
API Support
|
Post subject: Re: Standalone API Launch Remote Strategy Execution |
Post rating: 0
|
Posted: Mon 23 Sep, 2013, 09:17
|
|
User rating: ∞
Joined: Fri 31 Aug, 2007, 09:17 Posts: 6139
|
We are working on it right now.
|
|
|
|
|
hyperscalper
|
Post subject: Re: Standalone API Launch Remote Strategy Execution |
Post rating: 0
|
Posted: Tue 01 Oct, 2013, 17:32
|
|
User rating: 98
Joined: Mon 23 Jul, 2012, 02:02 Posts: 656 Location: United States, Durham, NC
|
I am ready to deploy my Remote Strategies Live, and have a few design questions.
My current plan is simply to "clone" the BOT instance as follows:
Firstly, compile BOT.java -> BOT.jfx (associated with BOT.xml for its configuration).
Then "clone" BOT.jfx through copy/rename to BOT2.jfx, BOT3.jfx, etc.
Also, BOT.xml "cloned" through copy/rename to BOT2.xml, BOT3.xml, etc.
Each BOTx is then launched using Remote Run and its specific params are configured manually at initial launch, but I will be able to change those parameters at runtime through a "remote console" facility which I have custom programmed.
At runtime, the Console is able to communicate with all of the running BOTs. Initially, no BOT will trade until it has been enabled by my custom Remote Console, after is has been started, for safety.
This Console uses the IEngine.broadcast(topic, message) mechanism through a custom CommsManager facility, so that I am able to control each individual BOT's runtime parameters as it continues to run, and receive information from any/all of the BOTs to the Console. (The CommsManager automatically "paces" the IEngine.broadcast messages to conform with minimum delays.)
I WILL ALSO BE USING THE API FOR REMOTE RUN WHEN IT IS READY.
But somehow I have the feeling that "copy cloning" the BOT.jfx may not be the right approach. So far, I don't know of any way to uniquely identify BOTx.jfx instances, or to have a unique BOTx.xml configuration file. Is there another/better way ?
I'd like some advice whether this approach is OK, and also, please...
WHAT WILL THE REMOTE LAUNCH API SUPPORT? I assume I will need to use the Standalone API to use this facility when it's available.
Thanks for any information or tips, HyperScalper
|
|
|
|
|
API Support
|
Post subject: Re: Standalone API Launch Remote Strategy Execution |
Post rating: 0
|
Posted: Thu 03 Oct, 2013, 07:49
|
|
User rating: ∞
Joined: Fri 31 Aug, 2007, 09:17 Posts: 6139
|
|
|
|
|
hyperscalper
|
Post subject: Re: Standalone API Launch Remote Strategy Execution |
Post rating: 0
|
Posted: Thu 03 Oct, 2013, 14:58
|
|
User rating: 98
Joined: Mon 23 Jul, 2012, 02:02 Posts: 656 Location: United States, Durham, NC
|
API Support wrote: Thank you so much, but methods to discover or iterate through running Strategies, and to manage them, is also needed. Please look into functionality more than simply the IClient.startRemoteStrategy and please ensure that we can both start and IClient.stopRemoteStrategy(...) as a minimum. That would require the ability to discover running instances, I think. The JForex platform has great difficulty dealing with situations in which the Strategy Remote launch times out or fails. It then becomes very confusing as to what is actually running, and whether the initialization of Parameters is correct for each instance, as I have reported elsewhere. viewtopic.php?f=16&t=50129Thank you very very much for this, HyperScalper
|
|
|
|
|
API Support
|
Post subject: Re: Standalone API Launch Remote Strategy Execution |
Post rating: 0
|
Posted: Thu 03 Oct, 2013, 15:37
|
|
User rating: ∞
Joined: Fri 31 Aug, 2007, 09:17 Posts: 6139
|
The started strategies will be available with the current functionality IClient.getStartedStrategies, which will include the local and remote strategies started by the current process. Likewise one will be able to stop a remote strategy by using the IClient.stopStrategy method. In order to manage remote strategies started from other processes, one will need to use the platform.
|
|
|
|
|
hyperscalper
|
Post subject: Re: Standalone API Launch Remote Strategy Execution |
Post rating: 0
|
Posted: Thu 03 Oct, 2013, 16:34
|
|
User rating: 98
Joined: Mon 23 Jul, 2012, 02:02 Posts: 656 Location: United States, Durham, NC
|
API Support wrote: The started strategies will be available with the current functionality IClient.getStartedStrategies, which will include the local and remote strategies started by the current process. Likewise one will be able to stop a remote strategy by using the IClient.stopStrategy method. In order to manage remote strategies started from other processes, one will need to use the platform. Thank you. Please in a future release allow for management of all Remote Strategies for the Account, and not just those launched from the standalone API client process. In other words, the same functionality that the JForex platform implements with respect to Remote Run. Again, thanks for providing Remote Management functions in the API 2.9.4 HyperScalper
|
|
|
|
|
hyperscalper
|
Post subject: Re: Standalone API Launch Remote Strategy Execution |
Post rating: 0
|
Posted: Thu 17 Oct, 2013, 20:51
|
|
User rating: 98
Joined: Mon 23 Jul, 2012, 02:02 Posts: 656 Location: United States, Durham, NC
|
API Support wrote: The started strategies will be available with the current functionality IClient.getStartedStrategies, which will include the local and remote strategies started by the current process. Likewise one will be able to stop a remote strategy by using the IClient.stopStrategy method. In order to manage remote strategies started from other processes, one will need to use the platform. I'm waiting to upgrade until this is available in the API. What version, and when is it likely to release? HyperScalper
|
|
|
|
|
|
Pages: [
1
]
|
|
|
|
|