Could I trouble anyone to give me a quick message flow diagram when the OVER disposition is invoked in the OB TPS? In my testing it’s not working quite as I expected.
Check out the attached diagram from a previous Cloverleaf conference or class. It provides a good visual of what happens in an outbound thread. Remember that an OVER msg disposition instructs the engine to put the msg on the PRE-tps queue in the opposite direction. The PROTO disposition will place the msg on the POST-tps queue, opposite direction.
If you need assistance with the proc, just let me know.
I did look at this from my class booklets — okay, so an OVER disposition in the OB TPS stack should place the message on the pre IB TPS queue. Doesn’t that mean, then, that you can set up routing as normal in that thread and route messages accordingly?
Thread 1 —> Thread 2 (“over” in OB TPS) —> Thread 3
A few weeks back we had a thread that discussed how to do what you are speaking about. Bottom line was that is could be done but usually there is a “cleaner” way to do it with minimal impact to performance.
Check out this link for more information. Let me know if it makes sense.
Thank you David. Actually I was looking for this but couldn’t find it in a hurry. It did give me what I needed — I wasn’t setting the source thread to the middle thread along with the over disposition.
In some cases I do use the “cleaner” method, but in this particular instance I really need to use this setup.
Thanks again.
Author
Replies
Viewing 3 reply threads
The forum ‘Cloverleaf’ is closed to new topics and replies.