|
Home > Archive > BizTalk Server Orchestration > June 2005 > BizTalk 2004 :: Correlation :: "Could not find a matching subscription for the me
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
BizTalk 2004 :: Correlation :: "Could not find a matching subscription for the me
|
|
|
|
Hello everyone,
Maybe someone knows why I am having this correlation problem?
I send an xml doc that gets converted to a flat file.
I expect a response, with a file name that I have control over. I have set
up a correlation set with FILE.ReceivedFileName as the correlation type.
I am setting the file name to:
FLAT_FILE_SENT(FILE.ReceivedFileName) = @"D:\recv\REPLY" + uniqueNumber +
".REPLY";
In the subscription viewer I see the XLANG/s: item which corresponds to the
receive port (the reply) and its set correctly, it shows the filename I set.
In the send port subscription, I see nothing except SPTransportID. Is this
normal?
From all the posts I have read I am doing everything correct. The only
thing I dont understand is the isPromoted = true setting, is that
specifically related to promoted properties? If not, where is that setting?
Thanks,
BA
| |
|
|
I dont understand my problem:
I am trying to correlate on FILE.receivedFileName and I cannot. The
original post describes my setup...
I am digging deeper and still nowhere...
I made an isolated orchestration to test correlation only, simplified it (no
ff conversion, just xml with no promoted properties)
Same result. What am I missing?
It doesnt makse sense, since I see a subscription in the subscription viewer
for the message I am expecting:
XLANG/s:BizTalk_Orchestration1{fb5ed20f-3051-4225-b0f6-7382ac308634}
Port_corr2
I am dropping a file in the folder with the correct file name expected and
nothing....
I am getting nervous, I have a release....
"BA" <biztalk.architect@gmail.com> wrote in message
news:42afdde7$0$1373$5fc3050@dreader2.news.tiscali.nl...
>
> Hello everyone,
>
> Maybe someone knows why I am having this correlation problem?
>
> I send an xml doc that gets converted to a flat file.
>
> I expect a response, with a file name that I have control over. I have
> set up a correlation set with FILE.ReceivedFileName as the correlation
> type.
>
> I am setting the file name to:
> FLAT_FILE_SENT(FILE.ReceivedFileName) = @"D:\recv\REPLY" + uniqueNumber +
> ".REPLY";
>
> In the subscription viewer I see the XLANG/s: item which corresponds to
> the receive port (the reply) and its set correctly, it shows the filename
> I set.
>
> In the send port subscription, I see nothing except SPTransportID. Is
> this normal?
>
> From all the posts I have read I am doing everything correct. The only
> thing I dont understand is the isPromoted = true setting, is that
> specifically related to promoted properties? If not, where is that
> setting?
>
> Thanks,
>
> BA
>
>
>
>
| |
|
|
Also, note, this post gets at my problem to an extent, but it doesnt offer
me a workable solution I can see.
http://www.caffedharma.com/tech/archives/000113.html
"BA" <biztalk.architect@gmail.com> wrote in message
news:42b04963$0$1344$5fc3050@dreader2.news.tiscali.nl...
>
> I dont understand my problem:
>
> I am trying to correlate on FILE.receivedFileName and I cannot. The
> original post describes my setup...
>
> I am digging deeper and still nowhere...
>
> I made an isolated orchestration to test correlation only, simplified it
> (no ff conversion, just xml with no promoted properties)
>
> Same result. What am I missing?
>
> It doesnt makse sense, since I see a subscription in the subscription
> viewer for the message I am expecting:
>
> XLANG/s:BizTalk_Orchestration1{fb5ed20f-3051-4225-b0f6-7382ac308634}
> Port_corr2
>
> I am dropping a file in the folder with the correct file name expected and
> nothing....
>
> I am getting nervous, I have a release....
>
>
>
> "BA" <biztalk.architect@gmail.com> wrote in message
> news:42afdde7$0$1373$5fc3050@dreader2.news.tiscali.nl...
>
>
| |
|
| This is turning into a bit of a running monolog, but oh well
When I open the message that fails in trying to correlate in HAT, the
ReceivedFile's isPromoted property is set to false.
That is obviously my problem. If the received file name is not promoted,
there is no way a correlation can take place, and thus the error makes
sense... its getting a message with the correct file name but since the
property is not promoted, it doesnt work.
Obvious question then, does anyone know how to change things so that the
isPromoted property is true instead?
Thanks
"BA" <biztalk.architect@gmail.com> wrote in message
news:42b04a96$0$1358$5fc3050@dreader2.news.tiscali.nl...
>
> Also, note, this post gets at my problem to an extent, but it doesnt offer
> me a workable solution I can see.
>
> http://www.caffedharma.com/tech/archives/000113.html
>
>
>
> "BA" <biztalk.architect@gmail.com> wrote in message
> news:42b04963$0$1344$5fc3050@dreader2.news.tiscali.nl...
>
>
| |
|
|
The solution, for anyone with similar issues is to do this:
1) Make yourself a custom pipeline component, follow these instructions:
http://geekswithblogs.net/synBoogaloo/
(I excluded the regex bit)
(if you have problems, this blog has lots of pipeline posts:
http://blogs.msdn.com/gzunino)
This will promote your receivedFileName property to work with correlation
2) Add a disassembler to your pipeline (either flat file or normal, whatever
you have, make sure you identify the message type)
---technically you can do this with a generic doc, my requirements were
different though
Make the new receive pipeline your pipeline on the message your waiting for.
3) add a delay shape, move your receive shape (the correlating one) inside
it and add a delay shape on the other side.... its hard to get rid of these
messages, so a delay will time things out.
If you have a similar problem and need help, I'll keep this thread
bookmarked.
BA
"BA" <biztalk.architect@gmail.com> wrote in message
news:42b0502f$0$1341$5fc3050@dreader2.news.tiscali.nl...
> This is turning into a bit of a running monolog, but oh well
>
> When I open the message that fails in trying to correlate in HAT, the
> ReceivedFile's isPromoted property is set to false.
>
> That is obviously my problem. If the received file name is not promoted,
> there is no way a correlation can take place, and thus the error makes
> sense... its getting a message with the correct file name but since the
> property is not promoted, it doesnt work.
>
> Obvious question then, does anyone know how to change things so that the
> isPromoted property is true instead?
>
> Thanks
>
>
>
> "BA" <biztalk.architect@gmail.com> wrote in message
> news:42b04a96$0$1358$5fc3050@dreader2.news.tiscali.nl...
>
>
|
|
|
|
|