by community-syndication | Apr 1, 2005 | BizTalk Community Blogs via Syndication
Originally BizTalk Server 2004 has the limitation of adding new EDI schemas. However SP1 now allows to add new schemas and the KB article 840113 describes how to implement EDI schemas for BizTalk. I had implemented new EDI schemas with the KB article. But I realized right away that some information is missing.
I summarized some additional information which the KB article doesn’t mention. I hope this would be helpful to someone who wants to implement EDI schemas, especially EDIFACT schemas.
by stephen-w-thomas | Apr 1, 2005 | Stephen's BizTalk and Integration Blog
In addition to all the other cool stuff available in BizTalk Server 2004 Service Pack 1 is the addition of the Additional Flat File Schema Properties to the schema properties window when working with Flat Files.
Now, properties like Allow Early Termination, Generate Empty Nodes, Lookahead Depth, Parse Optimization, and Suppress Empty Nodes can be set inside Visual Studios. This will eliminate the tedious and error prone manual editing of the schema using notepad. Error prone? Yep, I messed this one up once…
by community-syndication | Apr 1, 2005 | BizTalk Community Blogs via Syndication
I’ve been very busy for last two months. During that time, I made a converting tool for BizTalk Base EDI Adapter.
Originally, BizTalk Server 2004 had the limitation of adding new EDI schemas. However, BizTalk Server SP1 now allows to add new schemas. This tool generates XML schemas for Base EDI Adapter from some legacy artifacts. To be honest, this tool generates KEDIFACT XML schemas and KEDIFACT is a variation of EDIFACT. I uploaded 41 KEDIFACT schemas of 1911, 1921, 2911, and S93A directories. I guess you also can utilize these schemas for EDIFACT with same directories because KEDIFACT has very similar directories and message types as EDIFACT. I think it requires only small changes. If you have any problem to use them for EDIFACT, feel free to drop your message.
by stephen-w-thomas | Apr 1, 2005 | Downloads
Microsoft BizTalk Server 2004 supports the use of convoy message processing, a new messaging pattern. Convoys are a messaging pattern and not a feature of BizTalk Server 2004. A convoy is not something a customer can use, like the Rules Engine, but instead it is something that the business process dictates and requires.
This paper discusses examples of business scenarios that require convoy message processing. After establishing a business need through the scenarios, this paper explains basic convoy theory and the different types of convoy messaging patterns. This paper discusses a solution to each business scenario and reviews each included sample.
View this whitepaper online at: http://msdn2.microsoft.com/en-us/library/ms942189.aspx
