| Author |
Multiple Flat Files to the same recieve port
|
|
|
| I read an article online which said that a recieve location can have a
pipeline with multiple flat file disassemblers and the first one which
matches the incoming flat file will forward the message to the next
pipeline component. Each flat file disassembler will need a document
schema or a message type. But the recieve port also needs a port type
and indirectly message type.
So how can a recieve port have multiple flat file schemas associated
with it?
Sree
| |
|
| I think you are talking about custom pipelines. You can create multiple
custom pipelines with the same flat file disassembler but with different
schemas.
So you can create one receive port --> multiple receive locations --> set
different custom pipeline in each receive location --> but the FILE adapters
point to the same physical file folder.
But the implication is like what the document mentioned - the first custom
pipeline which picks up the file may not able to process the file because the
schema attached to that pipeline may not match the file's specification.
Do this answer your question?
"Sree" wrote:
> I read an article online which said that a recieve location can have a
> pipeline with multiple flat file disassemblers and the first one which
> matches the incoming flat file will forward the message to the next
> pipeline component. Each flat file disassembler will need a document
> schema or a message type. But the recieve port also needs a port type
> and indirectly message type.
>
> So how can a recieve port have multiple flat file schemas associated
> with it?
>
>
> Sree
>
>
| |
|
| Well what I am trying to do is, A process involves generation of
multiple files with different formats. I am wondering If I can have
them come thru same recieve port (different recieve locations may be)
and transform them.
Sree
wwx wrote:[vbcol=seagreen]
> I think you are talking about custom pipelines. You can create multiple
> custom pipelines with the same flat file disassembler but with different
> schemas.
>
> So you can create one receive port --> multiple receive locations --> set
> different custom pipeline in each receive location --> but the FILE adapters
> point to the same physical file folder.
>
> But the implication is like what the document mentioned - the first custom
> pipeline which picks up the file may not able to process the file because the
> schema attached to that pipeline may not match the file's specification.
>
> Do this answer your question?
>
> "Sree" wrote:
>
| |
| Jan Eliasen 2006-09-20, 7:36 pm |
| On 19 Sep 2006 11:39:20 -0700, "Sree" <sreejonn@gmail.com> wrote:
>Well what I am trying to do is, A process involves generation of
>multiple files with different formats. I am wondering If I can have
>them come thru same recieve port (different recieve locations may be)
>and transform them.
Hi
That isn't a problem. You cna have as many receiv elocations as you
want to, and each receive location will have a receive pipeline
attached to it. The pipeline will promote the messagetype property.
In your send port (which doesn't have a message type associated, as
you stated in your first posting), you can attach as many maps as you
like. BizTalk will look at the maps on a receive port and execute the
first map it meets that has the correct messagetype as source shema.
If no maps are found that matches the incoming messagetype, no map is
performed.
--
eliasen, representing himself and not the company he works for.
private email: jan@eliasen.dk
|
|
|
|