Reply Routing

This topic has 5 replies, 4 voices, and was last updated 10 years ago by Rob Abbott.

Creator

Topic
December 9, 2014 at 12:37 am #54488
Tony Benitz
Participant
I am doing a vaccination Query / Response from our Epic system to our State Registry (Oregon).

I have the Query working from Epic to the State, but I am having issues with the routing of the REPLY from the State.

I have the Route Replies tab with a Static route to the thread that is attached to the Epic Inbound response.

I get an error in the process log, because it is telling me I can ONLY route to the sending thread.

What gives?? Someone must have done this.. It seems like I am so close.

Please help.. Thanks

Tony Benitz – tbenitz@lhs.org
Creator

Topic

Viewing 4 reply threads

Author

Replies
- December 9, 2014 at 7:15 am #81700
  Max Drown (Infor)
  Keymaster
  A picture is worth a thousand words. Can you post some screenshots?
  
  Are you using CAA-WS 2.0? If so, there’s an example or routing in the ws_samples sample site that gets installed with the adapter.
  
  -- Max Drown (Infor)
- December 10, 2014 at 1:15 am #81701
  Tony Benitz
  Participant
  RESOLUTION 😀
  
  The issue was resolved by changing the DESTCONN metadata on the reply, then the message is sent to the new thread.
  
  Let me know if anyone is intrested in the details.. all the magic that makes it happen.
  
  Special Shout out to Bob Milfajt who sent me an email with the bread crumbs that lead to the solution.
  
  Thanks.. TonyB
- December 10, 2014 at 11:30 am #81702
  Jim Kosloskey
  Participant
  What release of Cloverleaf?
  
  I am not saying the product does do this but it should allow reply routing WITHOUT needing to touch anything other than configuration.
  
  I know I had to do something similar on 5.6 but have not tried Reply Routing on 6.0.0 (the release we are using now).
  
  Maybe I will give this a try when I get time and see if the same issue exists on 6.0.0.
  
  email: jim.kosloskey@jim-kosloskey.com 29+ years Cloverleaf, 59 years IT - old fart.
- December 10, 2014 at 3:25 pm #81703
  Tony Benitz
  Participant
  Right, that is what we thought as well. It would just work, but it didn’t
  
  Here is the version information
  
  Host Server Build Information:
  
  Version: 6.0.2.0P
  
  Date: Thu Feb 20 2014
  
  Time: 05:27:19 AM
  
  Platform: Windows_NT
  
  Java Vendor: Sun Microsystems Inc.
  
  JDK Version: 1.6.0_31
  
  Swing Version: 1.6.0_31
  
  RMI Version: 1.6.0_31
- December 19, 2014 at 9:45 pm #81704
  Rob Abbott
  Keymaster
  FYI, in 6.1 the reply routing paradigm has changed a bit.
  
  You can now tell the engine to route to a different destination by creating a reply route to that destination.
  
  Or you can have it use the old behavior (that you’re seeing – in 6.0 and below) where any replies are automatically routed to the original source – regardless of where you have reply routes specified.
  
  If you leave the DESTCONN workaround in place it should function appropriately with either choice.
  
  Rob Abbott
  Cloverleaf Emeritus
Author

Replies

Viewing 4 reply threads

The forum ‘Cloverleaf’ is closed to new topics and replies.