| Author |
Message |
|
|
Can you provide more details as to what you mean by "this tool"? We do have a FIX based simulator - as described here. Are you looking for something else?
Thanks,
Yoram
|
 |
|
|
Hi,
In mainline/trunk we already moved on to using esper-3.0.0 so you can take a look at that - we had to make minor changes to make it work though. If you can wait couple of weeks our next release will include esper-3.0.0. Right now trunk is still changing so I don't recommend using that as it is just yet. Soon as we release the new version we will also update the documentation of how to build the platform from the new release tag.
Thanks,
Yoram
|
 |
|
|
Hi,
1. Check our Simulators info here: http://www.marketcetera.org/confluence/display/MPIC/Marketcetera+Simulators
Essentially you need to connect to Market data interface (port 7003) to see the trade events - by default you are connected to Random Market Data Simulator (port 7004) - as it generates more data.
2. We don't provide DOB in our simulator and in the product itself. We plan to add support for DOB in the product in our next release. The simulator will not have DOB in that release but our Bogus Market Data Simulator feed will.
Thanks,
Yoram
|
 |
|
|
Hi,
The sending time shown is indeed up to seconds, but in the database and in the FIX message itself the accuracy is in ms. You can see that if you look in the "FIX Message Details" (right click in the FIX Messages windows and choose "View FIX Message Details"). At the bottom of that window you can see the FIX message fields and the FIX message timestamp.
As for the issue itself - we have seen it here as well and we are tracking it. As you mentioned it doesn't happen everytime - but we will try to solve this in our next release. Can you please file a ticket in our JIRA issue tracking system - http://www.marketcetera.org/jira - and provide as many details as you can. If possible please provide the FIX Message details of both the NEW and PENDING_NEW.
Thanks,
Yoram
|
 |
|
|
We didn't try Sun Solaris here in Marketcetera. If anyone did it would be great if you can post/share your experience here in this forum.
Thanks,
Yoram
|
 |
|
|
Hi Larry,
First let me clarify that our WS interface is not finalized and might change between minor versions. As you probably know we use client APIs to connect our clients to ORS (also see this writeup).
That being said and specifically addressing your question the service name url you are looking for is http://localhost:9000/org_marketcetera_client_Service?wsdl
Note that you will need to take additional steps, for instance you will need to login to get a valid session id - that service is available in http://localhost:9000/org_marketcetera_util_ws_stateful_AuthService?wsdl. Not sure whether additional steps are needed - but you can always check the source code and try to follow our Java WS code.
Hope this helps.
Thanks,
Yoram
|
 |
|
|
Please use the attached file and copy it into client/META-INF in your dev env. That should allow you to run Photon from source without internet connectivity.
Thanks,
Yoram
|
 |
|
|
Hi all,
We now have an updated contribution wiki page with details of how to contribute and updated list of projects/features we could use your help with:
http://www.marketcetera.org/confluence/display/MPIO/Contribute
Looking forward to your suggestions, participation and contributions!
Thanks,
Yoram Talmor
VP Engineering
|
 |
|
|
Udi,
We have a KB writeup on how to do broker specific custom FIX dictionaries here which also links to this page with more details on custom FIX dictionary.
You can also check Quickfix/J user manual here.
I don't really know what you mean by "suppress a tag" and I assumed that is something which is broker specific hence my previous comment about services we offer for broker certification.
As for Ildefons comments about us not being an open source project - I would encourage you to look around and see what we do offer as an open source project from code, documentation, help and community interaction perspectives (and much more). Like many open source projects we don't have infinite resources and as a company we do offer paid services. However, this doesn't and shouldn't prevent members in the community from developing their own solutions using our open source platform (and we gladly help as much as we can) - as we do the same. Those combined efforts help us improve the platform. Ofcourse there is always room for improvement and that's where we look to our community members to help and contribute back with advice, answering other members questions, code contributions or suggestions - so we can share it with all and make it an even better open source project.
As always we appreciate your feedback and suggestions.
Thanks,
Yoram
|
 |
|
|
You should file this in our issue tracking system here:
https://www.marketcetera.org/jira/secure/CreateIssue!default.jspa
Thanks,
Yoram
|
 |
|
|
Udi,
Whenever you connect to a specific broker you need to go through a process we call broker certification - basically building a custom FIX dictionary for that broker. It is hard to solve such issues in a forum discussion, since they are so broker specific and do require iterative custom work to get done. We do offer paid services to help with such broker certifications - send an email to info@marketcetera.com for additional information.
Thanks,
Yoram
|
 |
|
|
I have been trying this a few times for the past couple of days. My conclusion is that tracert didn't really help me to identify when there is a real problem with connecting to the exchange simulator - classic case of false positive. Tools like ping and telnet directly to the exchange port seem more reliable - and those worked for me even when tracert didn't.
Thanks,
Yoram
|
 |
|
|
Currently we don't have concrete plans of what additional extensions we will make available for the strategy editor. Obviously feedback and suggestions are welcome. I recommend that you file suggestions/improvements/new features in our issue tracking system:
https://www.marketcetera.org/jira/secure/CreateIssue!default.jspa
Please choose the correct project (in this case Photon) and the issue type (in this case improvement).
Thanks,
Yoram
|
 |
|
|
<ctrl>+F10 and then choose "show line numbers". Also, you can do <ctrl>+l (the letter L, not 1) to go to a specific line number. <ctrl>+<shift>+l (again, letter L, not 1) shows you a menu with additional shortcuts. I am sure there is more...
Thanks,
Yoram
|
 |
|
|
Hi Larry,
Can you provide more details as to what worked for you in this case (for those that might encounter the same problem in the future).
Thanks,
Yoram
|
 |
|
|