| Author |
Received File Size
|
|
|
| Hi All,
Is there a way to extract the size of the interchange(flat file in
my case)BTS received ?
Thank you
Pop
| |
| Martijn Hoogendoorn 2004-11-17, 2:46 am |
| On 16 Nov 2004 20:48:02 -0800, Pop wrote:
> Hi All,
> Is there a way to extract the size of the interchange(flat file in
> my case)BTS received ?
>
> Thank you
> Pop
Hi Pop,
Not as far as I know, the base schema for the FILE adapter has only 3
promoted properties:
AllowCacheOnWrite
CopyMode
ReceivedFileName
HTH,
Martijn Hoogendoorn
| |
| Greg Forsythe 2004-11-17, 5:48 pm |
| You extend the FFDisassembler pipeline component and add the file size to
the message context.
Use the example in the docs of the transactional FF disassembler and add the
property promotion code before calling the base.Disassemble method
For info on promoting properties in a pipeline component see:
http://blogs.msdn.com/scottwoo/arch.../19/187563.aspx
Greg
"Pop" <paul.p.mathew@gmail.com> wrote in message
news:a918884f.0411162048.51a14cdb@posting.google.com...
> Hi All,
> Is there a way to extract the size of the interchange(flat file in
> my case)BTS received ?
>
> Thank you
> Pop
| |
| Neal Walters 2004-11-19, 5:48 pm |
| Are you in an orchestration? Couldn't you load the message into an
XmlDocument then check the size/length of the XmlDoc.OuterXml?
Neal Walters
http://Biztalk-Training.com
| |
| Greg Forsythe 2004-11-19, 5:48 pm |
| The Xml document size will be different from the original flat file size
You would also face an issue if the original document is disassembled into
multiple messages or an inbound map was used.
Greg
"Neal Walters" <NealWalters@discussions.microsoft.com> wrote in message
news:2EC81EC6-93C3-4C0B-90AC-74D3487D1A95@microsoft.com...
> Are you in an orchestration? Couldn't you load the message into an
> XmlDocument then check the size/length of the XmlDoc.OuterXml?
>
> Neal Walters
> http://Biztalk-Training.com
>
|
|
|
|