Is msgmetadata preserved over a tcp/ip thread pair?

Peter,

From an engine perspective, once the data leaves your outbound thread, the metadata would be gone, as thread C would be like any other inbound connection to an external system; the metadata on the message would simply be comprised of thread C’s information.

Another way to handle this (using the A, B, C thread example above) is to have the outbound TPS of thread B change the SOURCECONN metadata field to the name of thread B and return the message with a disposition of OVER, then you can create a route from thread B to thread C and you don’t have to go through a loopback TCP/IP connection. This will preserve the message metadata.

We’ve got some interfaces like that. In that case you can use inter-site routing. Make B a destination thread. Make C a public thread. We’re still on version 5.8, so the messages are put on the outbound queue, and we use the OVER disposition/SOURCECONN metatdata change to put the message onto the inbound queue and route the message somewhere else in the second site. I think version 6 lets you have public threads that put their incoming messages on the inbound queue, but I might be wrong.

David,

Your post got me looking (we are on 6.1.1), and low and behold there is an option on the thread configuration Properties tab:

Messages routed to this connection treated as inbound

From the documentation:  Select this to make the destination behave as inbound, not outbound, so that you can route messages delivered to the destination site.

Cool!

Jim Cobane

Henry Ford Health