Re: ACK/NACK for Direct port binding

Home Page Forums BizTalk 2004 – BizTalk 2010 ACK/NACK for Direct port binding Re: ACK/NACK for Direct port binding

#21305

Thank you for your Reply Stephen,

Maps works fine. If remove direct recive, that is trying to get the ACK from message box, then my project works fine. I guess may be issue with transfering context property. Let me be more detail here

I have messages. A- Our request(commen for all vendor), B- Vendor request(each vendor have different) C-Vendor response and D-Our response(commen). I send the A to Direct 2 way port, it will get mapped with B at port and send it to vendor. Vendor response C will be mapped to D and get into orchestration. I promote Vendor ID, Vendor No, ACKRequired and CorrelatedToken to our request A.  We dont map Vendor ID or Vendor No to Vendor request B. So non of the message B,C or D have Vendor ID or Vendor No.  Do you think this might be the reason for the issue?

How can i transfer the context property to all other 3 messages? I dont think i can do it to vendor msgs B or C since I dont them in orchestration. would it be ok to promote them to our messages A and D? Since response D wouldn’t constrcut untill i get response from partner, it is going to be bit more works on orchestration if i want to promote those propety to it.

I just found your “Dynamic Transforms” posting.  It looks like perfect solution for my case however, I dont understand the concept. So I need to do more research on how it works and how to do.

Siva