- This topic has 5 replies, 1 voice, and was last updated 9 years, 5 months ago by
.
-
Posts
-
-
I have a request and response port and this port will follow the correlation.
I validate the schema in the orchestration and response back to the response port.
My problem is that, when we receive invalid schema, the response is correct but the subscription is missing so when the client sent the same correlation id but with valid schema, they will get no subscriber error. How can i enable back the subscription based on the correlation?
appreciate any help.
Thanks in advance
-
Hi,
1. I like your avatar!! :))
2. In one of our project, we used some field in an incoming schema, as a field served for for correlation. It was promoted in receive pipeline, and the value of that field was set to context of an outgoing message.
-
Hi Yonathan,
thanks for your reply.
1. thanks and it quite similar to yours [:D]
2. yes, i created a correlation by using some filed in the incoming message but the problem i’m having is that when the received port received the message, the subscription(based on correlation) is gone but the message is having a value which not following the schema so we response back with the error. and now i want to enable back the subscription(receive port) so that the external system can sent the same request with the correct value in the message. right now when the system response back with the correct message, BizTalk will response with no subscriber error.
-
I think about something: is you get malformed message, maybe to make correlation based on more than one property? transport type + message type + something else?
-
yes my correlation is based on two value in the message : reference no + agency ID. Is this the cause of it?
-
-
-
-
-
- The forum ‘BizTalk 2004 – BizTalk 2010’ is closed to new topics and replies.