Are you handling the response back from the server? If not, the response ends up in state 1 of your outbound thread and ends up in your error database because there are routes defined in the outbound thread.
Do you have the tcl proc dumpMsg from your sample sites. They have this proc located in both the tps Outbound Data and the tps Inbound Reply with await replies enabled. I found this used in the sample configurations. Hope this helps….
Does the zocdoc_patient_search_response proc KILL the response? If not, consider adding hcitpsmsgkill after that proc. In fact, just to test, try adding that proc.
Corrie, if you want to, email me a BOX up of the interface (manually include the XML config from the javadriver config) and I’ll take a closer look at this for you. It’s hard to see exactly what’s going on without seeing the configs in this case.
ok. I opened a ticket with Infor and they told me to put the client and server thread in different processes and to clear the USERDATA between the 2 threads
I added a proc that clears user data to the inbound data section of the inbound thread and inbound replies section of the outbound tab and sent a message from the web and got soooo close.
Now the messages are going from the web to clover out to the service then back into clover and back to the original source thread….beautiful
But then I get the error message below….
Call to “doReply” returned error string “BADDATA missing driver control which is required to process messages with ToCloverleafLink class”. Returning bad send to engine.
1. make sure ws-client thread and ws-server thread are in different processes
2. clear out USERDATA between threads – I added a proc to clear USERDATA on the Inbound Data section of the Inbound tab of the Inbound thread and added the same proc on the Inbound Replies section of the Outbound tab of the Outbound thread.
3. on the client thread/outbound thread there is an option under the General tab to copy driver control.
Author
Replies
Viewing 9 reply threads
The forum ‘Cloverleaf’ is closed to new topics and replies.