Hi Amit,
The BizTalk Tracking database can keep the message in their original
format (flat file, EDI, binary, ...). In the receive port tracking
options, you can select : "Track Message Bodies - Request message
before port processing".
In this case, you track the original message.
If you select "Track Message Bodies - Request message after port
processing", you can also track the message after the pipeline, so in
this specific case, the message can be in XML format, depending on the
pipeline you use (XMLReceive, ...).
Notice : if you use a PassThroughReceive pipeline, the message before
the port processing and after the port processing remains the same.
Also notice that if you have a map on the receive port, the message
after the port processing is the message after the transformation.
Feel free to ask more questions if you want.
David Grospelier
blog.noveli.fr
On Mar 9, 12:55*pm, amit chaudhary <amit1...@gmail.com> wrote:
> Hi Dav,
>
> It may be the requirement to keep the message coming from external
> parties like invoices from supplier just for government regulations. I
> suppose in this case we have to keep the message in original format as
> sent by external party. In this case I suppose we wouldn’t be to able
> to use the tracking db to keep the message as this db will keep the
> message in XML format( after pipeline transformation) instead of
> original format. what would be the best practice to archive message in
> this case?
>
> Regards
> Amit K
>
> On Feb 25, 1:38*pm, dgrospelier <dgrospel...@gmail.com> wrote:
>
>
>
> > Hi,
>
> > I'm not sure to understand your needs but if you want to have a backup
> > of files received or sent by BizTalk, my proposal is to use the
> > BizTalk Tracking. You can set up BizTalk to store the body of the
> > messages going through the Message Box. The messages bodies are stored
> > into the BizTalkDTADb database and you can use the BizTalk
> > Administration Console to view them and also to save them to disk.
>
> > However, I advices you to have two separate servers (one for BizTalk
> > and one for SQL Server) : for performance concerns but also for high
> > availability scenarios because in the future you would be able to add
> > a new BizTalk Server on the same BizTalk group.
>
> > David Grospelier
> > blog.noveli.fr
> > d...@noveli.fr
>
> > On Feb 24, 8:51*pm, mj <m...@newsgroup.nospam> wrote:
>
> > > Hello,
> > > I am trying to find the correct way to set things up for BizTalk, currently
> > > we
> > > have a server dedicated to the BizTalk server and its databases (theyall
> > > sit on the
> > > same server), the same server also houses the xml and csv files that BizTalk
> > > creates. *My question is, should we be saving the files that BizTalk creates
> > > some where else - like on another server separate from the server that
> > > BizTalk and it's database sits on? *What is considered good practice for
> > > BizTalk? *Any inputs or comments will be really helpful.
> > > Thank you in advance!- Hide quoted text -
>
> > - Show quoted text -