04-27-06 12:26 PM
NWOP,
Architecturally, BizTalk provides several alternatives for this. DTA
tracking, for one, can be leveraged to capture and store BizTalk message
bodies (and/or message properties) during different stages of processing to
the BizTalk DTA database. From there, you can implement different
archiving and purging schemes. With BizTalk Server 2006, this story has
improved tremendously and makes it very easy to configure these archiving
and purging jobs. An A&P QFE has also been backpropped to BizTalk Server
2004 so that existing customers can also benefit from these new features.
Business Activity Monitoring (BAM) is another solution which provides a
more robust, performant, and scalable model for document tracking than
traditional DTA tracking, and this can also be considered. Lastly, custom
archiving code can be developed, such as the Archiving Pipeline Component
Jeff Lynch describes here:
http://codebetter.com/blogs/jeff.ly.../08/142537.aspx
Hopefully this will give you a better idea as to the different options you
have for tracking.
HTH,
Doug Girard [MSFT]
Note: This posting is provided "AS IS" with no warranties, and confers no
rights.
--------------------
>Thread-Topic: architectural question
>thread-index: AcZn4X8KzigeLZyvS3+TBcj8YB79yQ==
>X-WBNR-Posting-Host: 63.225.252.220
>From: examnotes
<newworldorderpiggies@discussions.microsoft.com>
>Subject: architectural question
>Date: Mon, 24 Apr 2006 13:56:02 -0700
>Lines: 11
>Message-ID: <1A5F834D-57B4-48C4-AEEC-F1BA38EA8067@microsoft.com>
>MIME-Version: 1.0
>Content-Type: text/plain;
> charset="Utf-8"
>Content-Transfer-Encoding: 7bit
>X-Newsreader: Microsoft CDO for Windows 2000
>Content-Class: urn:content-classes:message
>Importance: normal
>Priority: normal
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.1830
>Newsgroups: microsoft.public.biztalk.general
>Path: TK2MSFTNGXA01.phx.gbl
>Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.biztalk.general:36920
>NNTP-Posting-Host: TK2MSFTNGXA01.phx.gbl 10.40.2.250
>X-Tomcat-NG: microsoft.public.biztalk.general
>
>I will be creating a very large number of outbound EDI transmissions and
want
>to be able to store those messages indefinitely after they are sent. I
was
>considering zipping up the message(s) into a zip file to store them but
was
>wondering if there was a better way to do this. I've been lead to believe
>that if I try to store them in the database it'll end up slowing down the
>server (which seems obvious) so that doesn't sound like an option but I'm
>finding it hard to believe there isn't something better than zipping them
up
>into a file.
>--
>Thanks to any and all!
>NWOP
>
[ Post a follow-up to this message ]
|