Author |
Message
|
wbi_student |
Posted: Tue Jul 26, 2011 2:17 am Post subject: FIX server integration using the broker |
|
|
Novice
Joined: 25 Jul 2011 Posts: 13
|
Hi,
Anyone try talking to a fIX server and initiating a fix session using the broker? my understanding is that one would need to send the logon message 35=A, send the fix data and then the logout message (MsgType=5 or 35=5).
any further pointers as to how one could go about setting this up?
Cheers |
|
Back to top |
|
 |
mqjeff |
Posted: Tue Jul 26, 2011 4:44 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008 Posts: 17447
|
What protocol does the Fix server use to communicate? |
|
Back to top |
|
 |
Ric-Tic |
Posted: Tue Jul 26, 2011 5:23 am Post subject: Re: FIX server integration using the broker |
|
|
Apprentice
Joined: 18 Nov 2003 Posts: 38 Location: Zurich, Switzerland
|
wbi_student wrote: |
Hi,
Anyone try talking to a fIX server and initiating a fix session using the broker? my understanding is that one would need to send the logon message 35=A, send the fix data and then the logout message (MsgType=5 or 35=5).
any further pointers as to how one could go about setting this up?
Cheers |
The Session is more likely to be:
Initiate LogonType 5
Receive Logon Acknowledgement
Send application message
Send Logout
Receive Logout Acknowledgement
And one should allow for Resend Requests and Rejects in the event of non-receipt or invalid messages |
|
Back to top |
|
 |
wbi_student |
Posted: Tue Jul 26, 2011 6:37 am Post subject: |
|
|
Novice
Joined: 25 Jul 2011 Posts: 13
|
so how would i go about creating this message flow or set of flows? Im wondering what kinf nodes would allow me to send this sequence of messages whenever I receive a FIX message on the input node? is this better done with a java compute or custom node? |
|
Back to top |
|
 |
mqjeff |
Posted: Tue Jul 26, 2011 6:42 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008 Posts: 17447
|
wbi_student wrote: |
so how would i go about creating this message flow or set of flows? Im wondering what kinf nodes would allow me to send this sequence of messages whenever I receive a FIX message on the input node? is this better done with a java compute or custom node? |
You would use transformation nodes to produce the relevant messages and then request nodes to send the relevant messages and receive the relevant responses.
Which nodes depends, again, on WHAT TRANSPORT DOES FIX USE? |
|
Back to top |
|
 |
wbi_student |
Posted: Tue Jul 26, 2011 7:31 am Post subject: |
|
|
Novice
Joined: 25 Jul 2011 Posts: 13
|
this is just FIX over TCP/IP. So Im thinking that would be TCPIPclientOutput nodes. but how would I order the mesges to be sent in that order in the flow when a fix message arrives at the input. i.e for a given input message, send a logon, payload and then logoff? |
|
Back to top |
|
 |
wbi_student |
Posted: Tue Jul 26, 2011 7:33 am Post subject: |
|
|
Novice
Joined: 25 Jul 2011 Posts: 13
|
i.e how would I do this ordering for a given input :
Initiate LogonType 5
Receive Logon Acknowledgement
Send application message
Send Logout
Receive Logout Acknowledgement |
|
Back to top |
|
 |
mqjeff |
Posted: Tue Jul 26, 2011 7:35 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008 Posts: 17447
|
MqInput->Compute1->TCPIPClientOutput->TCPIPClientReceive->Compute2->TCPIPClientOutput->TCPIPClientRecieve.... |
|
Back to top |
|
 |
wbi_student |
Posted: Tue Jul 26, 2011 7:56 am Post subject: |
|
|
Novice
Joined: 25 Jul 2011 Posts: 13
|
How could I do the logon/ack and logoff operations independent of the fix arrival? so that I can send the fix messages as they arrive to the fix server instead of logon/logoff every time. should I have say 3 'branches' to the same flow from the MQInput Node, so that the triggering event would be message arriving on the input node and then a flow order node to process the logon/ack , send payload and logoff operations? |
|
Back to top |
|
 |
wbi_student |
Posted: Tue Jul 26, 2011 8:04 am Post subject: |
|
|
Novice
Joined: 25 Jul 2011 Posts: 13
|
so, im thinking
--->ComouteNodeForLogon-->TCPIPClientOP
|
<---ComouteNodeForAck-->TCPIPClientIP
|
|
MQINPUT -->FLowOrder->-->ComputeNodeForPayload--->TCPIPClientOP
|
|
|--->ComouteNodeForLogff-->TCPIPClientOP |
|
Back to top |
|
 |
mqjeff |
Posted: Tue Jul 26, 2011 8:28 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008 Posts: 17447
|
I'd do it in one flow, and use an EXTERNAL variable to check to see if you need to log on or not.
MQInput->Compute1-(out1)->ComputeLogon->...
-(out2)-ComputePayload->.. |
|
Back to top |
|
 |
wbi_student |
Posted: Tue Jul 26, 2011 8:43 am Post subject: |
|
|
Novice
Joined: 25 Jul 2011 Posts: 13
|
but Im thinking I would need a flow order after the compute node to first logon and receive ack, then send paylod and then loggoff right? also how I handle the ack validation, i.e how/where would that fit into the flow. would it be second in the flow order sequence after the logon? |
|
Back to top |
|
 |
mqjeff |
Posted: Tue Jul 26, 2011 8:51 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008 Posts: 17447
|
I don't know fix enough to say.
My point was you should only logon, and logoff, when you need to - rather than every time.
This may or may not be true of the ack. |
|
Back to top |
|
 |
wbi_student |
Posted: Tue Jul 26, 2011 10:39 am Post subject: |
|
|
Novice
Joined: 25 Jul 2011 Posts: 13
|
so based on your explanation, im assuming that there is an implicit ordering int he compute node? i.e the branch originating out of the out1 terminal of a compute node is executed first before the payload branch and I wont need anythign explicit liek a FlowOrder? |
|
Back to top |
|
 |
mqjeff |
Posted: Tue Jul 26, 2011 10:43 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008 Posts: 17447
|
No, you would use PROPAGATE to control which one was called. |
|
Back to top |
|
 |
|