Hi Toli
Thanks for the info. The integration piece will be written in java so
using the org.marketcetera.core code to create the message is probably
the way to go. The other piece I'm not sure about is for account
information. By account, I don't mean trading account but instead mean
authentication account. Our current front end has the concept of
users, part of which is trading account information (including
position info) and part of which is authentication info. We currently
store that info in our database. I hoping that the shim that I write
will be able to pass of queries about the user account to the OMS as
well. Does the OMS currently have concepts like user account and
account positions? IF not, are there any plans to add it?
Jerald
On Feb 29, 2008, at 12:35 PM, Toli Kuznets wrote:
> Hi Jerald,
>
> This is great. Glad you are finding Marketcetera useful.
>
> As you've mentioned, the easiest way to integrate is to go through the
> JMS path: your front-end can create a FIX message and drop it on the
> message queue, and our OMS will pick it up.
>
> If your app is in Java, then the integration is dead simple - you can
> just use parts of the org.marketcetera.core code to create the message
> and send it, you can see the code for the OrderLoader as an example:
>
http://trac.marketcetera.org/trac.fcgi/browser/platform/trunk/orderloader/src/main/java/org/marketcetera/orderloader/OrderLoader.java> For the OrderLoader, we use Spring to configure a "JMS Adapter" and
> use that to drop a QuickFIX/J FIX message on the "oms-commands" queue.
>
> If your front-end is in C++/C# you can use the Marketcetera COM
> component (
http://trac.marketcetera.org/trac.fcgi/wiki/Marketcetera/dotNetSupport> ) to connect to the OMS and send messages.
>
> And if that doesn't work, you can use any of the other ways to
> integrate with ActiveMQ to create and drop a message on the bus:
>
http://activemq.apache.org/cross-language-clients.html>
> All you need to do is
> 1. connect to Marketcetera JMS server (on tcp://<machine>:61616 by
> default)
> 2. create a FIX message, drop it on the oms-commands queue
> 3. Listen for execution reports on the oms-messages topic.
>
> Meanwhile, the Tradebase picks up copies of the same execution reports
> off the trade-recorder queue and writes them to the database.
>
> Hope this helps. Would be happy to help you with your
> development/brainstorm - give us a call at 415-398-2644 if you have
> any questions.
>
> toli
>
>
> On 2/29/08, Jerald Dawson <
[hidden email]> wrote:
>> Hi There
>>
>> I am looking at writing an piece of software to integrate the m-etc
>> backend (OMS, Tradebase, etc) into an existing frontend we own. I'm
>> curious about how I would get started doing that. I'm assuming I
>> would
>> have to write something that integrates with the activeMQ stuff in
>> OMS. I'm not real familiar with activeMQ so any pointers would be
>> appreciated.
>>
>> Thanks
>>
>>
>> Jerald Dawson
>> _______________________________________________
>> Marketcetera Developers mailing list
>> Marketcetera Documentation:
http://trac.marketcetera.org>> To unsubscribe, go to
>>
http://lists.marketcetera.org/cgi-bin/mailman/listinfo/m-etc-dev or
>> send an email to
[hidden email].
>>
>
>
> --
> Toli Kuznets
>
http://www.marketcetera.com: Open-Source Trading Platform
> download.run.trade.
_______________________________________________
Marketcetera Developers mailing list
Marketcetera Documentation:
http://trac.marketcetera.orgTo unsubscribe, go to
http://lists.marketcetera.org/cgi-bin/mailman/listinfo/m-etc-dev or send an email to
[hidden email].
