Thanks for replying fjb,
I have found the solution now.
Actually I did correct thing in the first flow:
Set OutputRoot.HTTPRequestHeader.uniqueid=InputRoot.MQMD.MsgId;
But now I have found out that when it goes to second flow then uniqueid is received as Uniqueid(first alphabet changed to uppercase) so I am able to capture this in the second flow now .
It comes in the below tree:
InputRoot.HTTPInputHeader.Uniqueid
Maybe this is how the message flow functions for a custom header. But please let me know if you see any drawback in this solution.
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum