| Author |
file name correlation in Orchestration
|
|
| Wen Chi 2004-07-19, 5:52 pm |
| am trying out to do the file name correlation in
Orchestration.
I am not able to get filename correlation works.
In Orchestration , I set "FILE.ReceivedFileName" as
correlation type,
configure 2 receive shapes as parallel correlated shape to
receive files
from different folders
I got below error message after receive port recieved the
message.
The Messaging engine failed to process a message submitted
by adapter:FILE
Source URL:d:\customer\ecdemo\dttemp\*.xml. Details:Could
not find a
matching subscription for the message. . This error occurs
if the subscribed
orchestration schedule or send port has not been started,
or if some of the
message properties necessary for subscription evaluation
have not been
promoted. Please refer to Health and Activity Tracking
tool for more
detailed information on this failure
If I change the correlation type to a promoted property
from message
context, I don't hit any error.
Is there any extra configuration I need to do for file
name correlation?
| |
| Adrian Hamza[MSFT] 2004-07-19, 5:52 pm |
| See similar issue answered previously on this newsgroup.
===========
I think I found why your correlation is failing. FILE.ReceivedFileName
context property has the file name along with the complete path, e.g.
"C:\pickup\Input.xml" so unless your correlated message has the exact same
folder path as well, it will fail.
--------------------[vbcol=seagreen]
to[vbcol=seagreen]
I'll[vbcol=seagreen]
difference[vbcol=seagreen]
workaround[vbcol=seagreen]
--------------------
--------------------[vbcol=seagreen]
This posting is provided "AS IS" with no warranties, and confers no rights.
EBusiness Server Team
| |
| Wen Chi 2004-07-19, 8:48 pm |
| Thanks for your reply.
I understand the issue now.
Actually my goal is to correlate 2 files.
eg. 123H_123.txt , 123D_123.txt.
My previous thinking is to remove H/D and output the file
to different folder then let Xlang to pick them up.
According to your explanation, it looks it is impossible
now.
Is there any other way to correlate the 2 header and
detail files beside writing the filename to message itself?
Can I write a custom pipeline to promote a property?
Can Xlang see this property then see it to correlate?
Thanks for your great help
Wen Chi
>-----Original Message-----
>See similar issue answered previously on this newsgroup.
>===========
>
>I think I found why your correlation is failing.
FILE.ReceivedFileName
>context property has the file name along with the
complete path, e.g.
>"C:\pickup\Input.xml" so unless your correlated message
has the exact same
>folder path as well, it will fail.
>--------------------
FILE.ReceivedFileName property[vbcol=seagreen]
receive port?[vbcol=seagreen]
receive port[vbcol=seagreen]
orchestration instance found[vbcol=seagreen]
>to
problems with it.[vbcol=seagreen]
>I'll
messages itself[vbcol=seagreen]
and use it for[vbcol=seagreen]
the only[vbcol=seagreen]
>difference
adapter and instead it[vbcol=seagreen]
quick way to[vbcol=seagreen]
>workaround
>--------------------
>
>--------------------
microsoft.public.biztalk.orchestration:7174[vbcol=seagreen]
to[vbcol=seagreen]
the[vbcol=seagreen]
submitted[vbcol=seagreen]
Details:Could[vbcol=seagreen]
occurs[vbcol=seagreen]
started,[vbcol=seagreen]
evaluation[vbcol=seagreen]
>
>This posting is provided "AS IS" with no warranties, and
confers no rights.
>
>EBusiness Server Team
>
>.
>
| |
| Adrian Hamza[MSFT] 2004-07-20, 8:52 pm |
| It depends on your scenario if it's possible or not. Where do you
initialize your correlation set? Do you do that on a send port ?
If you initialize the correlation on a send port then you can make it work.
You must create a new message and set the FILE.ReceivedFileName property to
the same value as the value of the new message to be received (let's say
you receive message 123D_123.txt and this is the message for which you need
correlation).
SendMsg(FILE.ReceivedFileName) =
"c:\PathToDMessage\123D_123.txt";
This new message is the message that you send through the send port that
initializes the correlation set.
--------------------[vbcol=seagreen]
<Ie8rszbbEHA.2900@cpmsftngxa06.phx.gbl>[vbcol=seagreen]
This posting is provided "AS IS" with no warranties, and confers no rights.
EBusiness Server Team
| |
|
| Where do i set the FILE.ReceivedFileName property? i tried using the message assign shape but it shows errors for 'illegal ecsape ' where ever i have "\" in the path.
Thanks.
"Adrian Hamza[MSFT]" wrote:
> It depends on your scenario if it's possible or not. Where do you
> initialize your correlation set? Do you do that on a send port ?
>
> If you initialize the correlation on a send port then you can make it work.
> You must create a new message and set the FILE.ReceivedFileName property to
> the same value as the value of the new message to be received (let's say
> you receive message 123D_123.txt and this is the message for which you need
> correlation).
> SendMsg(FILE.ReceivedFileName) =
> "c:\PathToDMessage\123D_123.txt";
> This new message is the message that you send through the send port that
> initializes the correlation set.
>
> --------------------
> <Ie8rszbbEHA.2900@cpmsftngxa06.phx.gbl>
>
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> EBusiness Server Team
>
>
| |
| Adrian Hamza[MSFT] 2004-08-05, 8:08 am |
| Replace every \ with \\ and see if that works. You need to escape the
escape character "\". You do that by replacing it with "\\".
[vbcol=seagreen]
message assign shape but it shows errors for 'illegal ecsape ' where ever
i have "\" in the path.[vbcol=seagreen]
| |
| tinusonline 2004-12-21, 9:42 am |
| quote:
Originally posted by Adrian Hamza[MSFT]
If you initialize the correlation on a send port then you can make it work.
You must create a new message and set the FILE.ReceivedFileName property to
the same value as the value of the new message to be received
I tried this:
* Create a new message and set the ReceivedFileName to c:\test\file123.xml
* Send that message via a dummy send port to c:\trash hereby initializing the corrolation. When checking the context the ReceivedFileName property is still saying c:\test\file123.xml
* Drop the file 'file123.xml' in c:\test
I still get the error: no subscribtion could be found bla bla bla. has anyone got this working? |
|
|
|