Filed under: Biztalk 2004, Biztalk 2006, Configuration, Examples | Tags: Biztalk Server 2004, BizTalk Server 2006, Configuration, Correlation, Debugging, Heath and Activity Tracking, Monitor, Tracking, Tutorial
You can access an attribute or element in two different ways within Biztalk using ‘Distinguished Fields’ and ‘Promoted Properties’. A basic rule for ‘which to use’ would be: Always use a Distinguished Field, unless you need to route, track, or correlate on the content, then use promoted fields. (more…)
Filed under: Biztalk 2004, Biztalk 2006, Configuration, Examples | Tags: Adapter, BizTalk, Biztalk Server 2004, BizTalk Server 2006, Configuration, FileMask, Sendport, Tracking
It’s possible to set the filename of a messages that your are going to send out in the orchestration. Just set the ‘ReceivedFileName’ context property of the outbound messages that you created.
This should look like this:
OutboundMessage(FILE.ReceivedFileName) = "TheNewFancyFileName.xml";
After this you have to set the filemask in the sendport to %SourceFileName% (it’s case sensitive). The %SourceFileName% macro does not need an additional extension (like .xml or .txt) after it like the %MessageId% macro. (more…)
Filed under: Biztalk 2004 | Tags: BizTalk, BizTalk Server 2006, BTSNTSVS.exe, EDI, Heath and Activity Tracking, Schema
When you’re sending EDI messages with Biztalk 2006 and you need to modify one of the standard edi message, just modify the schema for your needs. Add new enumerations, change the sequence and rename the elements, but always change the namespace. So you can work with the normal (original) schema and the custom schema at the same time / server. (more…)
Filed under: Biztalk 2004, Examples | Tags: BizTalk, Biztalk Server 2004, Deploy, Labs, Mapping, Re-Deploy, Tutorial
The visual mapper of BizTalk that allows you to map an xml message to another xml message can be very handy when we’re talking about little xml files, but when you need to map a bigger xml file it gets very unstructured and difficult to maintain! (more…)
Filed under: Biztalk 2004, Biztalk 2006, Biztalk Errors | Tags: BizTalk, Biztalk Server 2004, Debugging, Deploy, Gacutil
So today I received the next error thrown by BizTalk Server in the eventlog. The problem is that there are two schemas deployed with the same namespaces. So after I checked all the projects that were installed, I found out that I added the same schema twice in one project…..
There was a failure executing the receive pipeline: “Microsoft.BizTalk.DefaultPipelines.XMLReceive” Source: “XML disassembler” Receive Location: ” C:\MessageStore\*.xml Reason: Cannot locate document specification as multiple schemas match the message type http://Schemas.InboundOrder#Root.
Filed under: Biztalk 2004, Examples | Tags: BizTalk, Biztalk Server 2004, BTSNTSVS.exe, Labs, SKD, Tutorial
The tutorials explain how to automate business processes within your company and among business partners, how to use Web services, and how to implement trading partner management and monitor business activities. (more…)
Filed under: Biztalk 2004, Biztalk 2006, Examples | Tags: BizTalk, Biztalk Server 2004, BizTalk Server 2006, Labs, MSDN, Virtual Labs Express
Start your BizTalk Server 2004 and 2006 experience with checking out all the virtual labs on MSDN. These labs really helps you to understand BizTalk Server. Virtual Lab Express is the fastest and easiest way to test drive Microsoft products and the Virtual Lab environment. These are 30-minute hands-on overviews of some of your favorite Microsoft products and developer tools. Try them out on-line now – no need to download full trial versions or dedicate test machines (more…)
Filed under: Biztalk 2004, Monitoring Biztalk | Tags: BizTalk, Biztalk Server 2004, HAT, Heath and Activity Tracking, Monitor, Tracking
If you like to clean up the tracking database of Biztalk Server 2004, you can just do this by running some little queries.
Open Query Analyzer and connect to the (Biztalk Tracking) BizTalkDTADb database. Then open the file called Purge_DTADB.sql in the next directory: “C:\Program Files\Microsoft BizTalk Server 2004\SDK\Samples\Admin\Database Maintenance”. Run this script (F5) and this script will create a storedprocedure called ‘dtasp_PruneTrackingDatabase’. This sp takes only a single parameter called: @PruneBeforeDate. Executing this SP causes the tracking data to be purged that was older then the given date (more…)
Filed under: Biztalk 2004, Covast EDI Accelerator, Problems | Tags: Accelerator, BizTalk, Biztalk Server 2004, Covast, CovastDB, EDI, repolock, repository
When you want to deploy the Covast Engine Input File (EIF) and you receive an error about an locked EDI repository, please read on for the solution. Covast locks his repository in the table called ‘parame’. So here lies also the possibility to ‘unlock’ your repository! (more…)
Filed under: Biztalk 2004, Biztalk Errors, Covast EDI Accelerator | Tags: Accelerator, BizTalk, Biztalk Server 2004, Covast, document definitions, EDI, Schema
When you like to change the maxlength parameter of an numeric element of an EDI message, you’ll find out that there is a dirty, nasty little bug in Covast. It can take you weeks to find out how this is actually working.
So as an example, we’re going to change and fix (max) length value of the 9308 Seal_Number element located in the EDI ‘IFTMIN D 99B Default UN’ message. First we open Covast Studio and go to the document repository. (more…)
