Covast’s Advanced B2B and ebXml Capabilities to be Delivered in Microsoft BizTalk Server R3

Covast has announced that Advanced B2B and ebXML(Electronic Business using extensible Markup Language) capabilities to be Delivered in Microsoft BizTalk Server R3.This is a great news for the customers who were using BizTalk 2006 and Covast Separately implementing EDI and B2B solutions.Please see the Covast Press release
Covast Adds ebXML Capabilities to Microsoft BizTalk Server 2006 R3
http://www.covast.com/news/press.asp?id=92


Covast’s Advanced B2B Capabilities to be Delivered in Microsoft BizTalk Server 2006 R3

http://www.covast.com/news/press.asp?id=91

Inbound File Name Hipaa Accelerator BizTalk 2006

I have seen many blogs to get the Source File Name in Hipaa Adapter as the Hipaa Accelerator removes the file name properties when it converts EDI to XML format and the SourceFileName Macro also doesnt work.To solve this issue follow these simple steps
1.Original file name is stored in Hipaa Accelerator database and the Table name is audin and the column name is origfilename.
2.In Audin Table we have icr as control Number,sid as sender Id ,rid as receiver ID and Date and time (HHMM) format is stored in these tables
3.For each EDI file we can have only control number and also Hipaa accelerator does not allow duplicate files to process as per its design
4.Create Store Proc on Hipaa Accelarto Db as
Select OrigFileName from audin where icr=@controlnumber and sid=@senderid and rid=@receiverid and date=@datefield and time=@timefield
5.We all know these values comes from the edi file either use a store procedure functoid in the map to get the filename or you can use an SQL port to execute the store procedure
6.Once we have the file name in the map or in orchestration we can write the inbound filename
Please email me or send me request if you have questions or comments on this article
Thanks

BizTalk Adapter for Oracle Database modifies the data in the DateTime field

There is a hot fix for this issue from Microsoft
http://support.microsoft.com/kb/921999

Donate 10 grains of Rice and Improve Your Vocabulary

I came to know thru Wade Wegner blog.
http://www.freerice.com/

BizTalk 2006 SQL Adapter on 64 bit machines

BizTalk 2006 SQL adapter will not run on 64 bit host instance so we need to create one more instance of BizTalk server that runs on 32 bit and assign sql adapter to run this 32 bit instance.BizTalk 2006 supported adapters on 64 bit machines is found on the link http://msdn2.microsoft.com/en-us/library/aa560166.aspx

Next issue we have seen is that when you run 32 bit program VS 2005 on 64 bit machines you will get the following error also
When trying to deploy BizTalk assemblies you will get this error

error DEPLOY: COM+ was unable to talk to the Microsoft Distributed Transaction Coordinator (Exception from HRESULT: 0x8004E00F)

There is an hot fix for the above issue.For more details
http://support.microsoft.com/kb/910907

How to split an XML message in BizTalk 2004/2006 using Document & Envelope Schemas

When you want split message into multiple xml documents we need to use envelopes and schema ,there is a good article by Jan where he explains step by step how to create envelopes in his blog.We came across this situation when we retrieved data from Sql adapter it was whole bunch of records and it has to be split into multiple xml documents for processing


http://weblogs.asp.net/jan/archive/2004/03/07/85259.aspx

Considerations When Creating BizTalk Projects

We had Covast EDI schemas about 29 MB in BizTalk Project and when we try to build it in Visual studio 2005 throwed error " CS0013 "Unexpected error writing metadata to file " the reason is the limitation of file size.Microsoft has recommended for 10 mb for a biztalk project.For more Information
http://msdn2.microsoft.com/en-us/library/aa561979.aspx