Hi,
Sample 259 drop the response due to the sample service does not provide
a proper request that can convert into FIX. But with a service that
sends a response with required values to create a FIX response,
execution(fill/partly fill) or an ACK can send back to the sender using
the FIX session created with Synapse and FIX client.
Please attach your Synapse confiuration to provide detailed information.
Regards
Asanka
PrgTrdr wrote:
I have cloned Sample 259 to implement a use case where a FIX client
communicates with a Web Service. The system is working well as far as 1)
establishing the FIX session from the client to Synapse, 2) Logon, 3)Sending
a New Order message, 4)performing an XSLT to create a WS request, 5)sending
the Request to the WS, 6)receiving back a Response from the WS, 7)performing
an XSLT to convert the SOAP response to an XML-encapsulated FIX message.
But then the response message never flows back to the FIX transport (I can
tell by examining the QuickFIX/J logs).
I am receiving (and converting) the WS Response message in a standard
"<out>" sequence. At the end I placed
<send>
<endpoint key="FIXProxy"/>
</send>
to see if that would make it work, but the message doesn't go out to FIX,
nor does it show up in the FIXProxy <outSequence> (I put some log mediators
in there to trace activity).
Sample 259 is one-way only (FIX->SOAP). Can someone give me an idea about
what needs to be done to make this two-way? Perhaps changes to the FIXProxy
configuration?
Thanks,
Bill
