[DAVID SPENSER]

Hi, Charlie.  I thought you had retired!!  Anyway, we want to send them messages…ADT and orders.  They work through this HTTP POST mechanism.  Cloverleaf supports that.  We have a URL and a port.  It looks like there’s a standard header defined.  I’m not sure if like a SOAP web service we need to put an envelope around the message.  Are there any necessary tclprocs that need to be added into the configuration?  How do we monitor ACKs?

[DAVID SPENSER]

Charlie, you said to set it up the same as an IB thread.  Did you mean as an OB thread?  If inbound how would you configure waiting for ACKs and resending messages?

[DAVID SPENSER]

Tom,

Thanks for the response.  Maybe I’m a little dense and the definitions are self explanatory, but I was hoping I could find more meaningful information on what those codes mean, what’s behind them, why they happen, are they transient, and do they need to be corrected?

[DAVID SPENSER]

Dan,

Perhaps I spoke too soon.  I believe we finally did get this resolved.  We are on version 5.4 of Cloverleaf.  Because of the way we have build our engine using Cloverleaf and components from BEA we had set up our listening ports as multiserver.  We found out that there was apparently a bug with multiserver that is supposedly fixed with version 5.6.  I believe we solved this problem by simply reconfiguring the listening ports as server.

[DAVID SPENSER]

Dan,

No, I never really got an answer.

[DAVID SPENSER]

Charlie,

Great code!  Is this done in the Inbound TPS rather than as a pre-proc to the translation?

[DAVID SPENSER]

Thanks, Mark.

I think I’ve come to realize (unfortunately) that you’re right.  Well, at least now I’ve got a direction!

[Author]

Replies