BizTalk

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

2008-10-14T08:30:00.000-07:00

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

2008-01-14T12:43:00.000-08:00

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

2008-01-04T08:27:00.000-08:00

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

2007-11-26T08:21:00.000-08:00

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

BizTalk 2006 SQL Adapter on 64 bit machines

2007-04-21T06:46:00.000-07:00

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

2007-02-08T08:58:00.000-08:00

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

2007-01-28T07:19:00.000-08:00

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

More about Biztalk 2006 Pass thru pipeline in a map,Deployment process,host instances

2007-01-03T06:24:00.000-08:00

I was working on a application where i need to use a pass thru pipeline and i need to apply a map to change a value in the incoming data, but the map didnt get applied in send port or receive port, the reason is when you use pass thru the maps will not get applied, work around ...
use orchestration and apply the map or create custom pipeline so that whole data is in xml type and apply maps in send port or receive ports.Same is the case when you use covast edi accelerator for biztalk we need to use covast pipeline components so that edi is converted into xml's....
Changing the file name in sharepoint adapter uses %filename% macro while all other adapters use %sourcefilename%, this can be done in expression shape such as message(wss.filename)=customname and use filename macro in sharepoint adapter..
I came to know that sharepoint 3 is not supported until bts2006 r2 if any one know has worked on this area please ping me on this post for sharepoint configuration

Biztalk deployment process and Host instances

Make sure biztalk host instances in dev and in prod environments are same,when you configure biztalk the host instances security levels are same if not when you try to import the binding file or an msi it will fail.You can change the biztalk server application as trusted in administration console by adding one more instance make that one has default process and we can change the original biztalk server application to trusted.Will need to change the receive handlers also...If you any one wants to know more about please ping on this forum...

Creating MSI application
Creating an application A and all your artifacts in respective folders such as pipelines ,maps ,schemas, orchestrations
And when you create application B and you want refer one of the components for eg pipelines in Application A than the pipleline component has to be in A, its confusing .......

BizTalk Native edi adapter doesnt support batching

When you have multiple ST's in GS envelope native edi adapter process only the first occurence of ST gets processed and this scenario we didnt capture at the last moment, i believe R2 will support batching process like hipaa accelrator and covast edi accelerators

Thats it for now

Edi support across the various releases of BizTalk Server.

2006-12-06T10:02:00.000-08:00

We were struck in changing GS segment value in native edi adapter Biztalk 2006 and it was supported in Biztalk 2000 and 2002 environment not in Biztalk 2004 or in 2006.The BizTalk 2006 R2 is supporting lot of edi features such debatching ,batching and also changing environment mode from P to T (Production to Test) and also changing at the envelope level in edi file.Here is an link which shows the comaparision across 2000,2002,2004,2006 &2006 R2 environment .Waiting for R2 release.....

http://blogs.msdn.com/biztalkb2b/archive/2006/11/10/evolution-of-edi-features-over-biztalk-server-versions-2000-to-2006-r2.aspx

Network Storage Routers

2006-11-04T07:16:00.000-08:00

I have been using laptop and an external USB hard drive. And whenever i want to connect external Hard drive or a Printer i was physically connecting to my USB ports. Later i was googling to find out is there a way of connecting the external hard drive to my PC without connecting the wires either bluetooth or so. I found that there are Wireless routers which are capable of connecting external hard drives where we can share the files across the network. All you have to do is just plug-in the hard drives in the USB ports of the router and wow now you can access your external hard drives or printers wirelessly(how convenient!). There are also some network hard drives which can connect to ethernet ports. Ofcourse i am not Networking guy though this technology would have existed long time back wanted to post this informaton as we are moving towards wireless technologies (wireless routers,Bluetooth etc.,) in our day to day practices.

List of bugs that are fixed in BizTalk Server 2004 Service Pack 2

2006-10-30T12:38:00.000-08:00

Service pack 2 has lot of fixes for BizTalk server 2004.for more information click link below
http://support.microsoft.com/kb/924330/en-us

Microsoft BizTalk Server 2004 Service Pack 2

2006-10-30T12:32:00.000-08:00

BizTalk Server 2004 Service pack 2 is available now.Prior to install this service pack 2 should have installed Service pack 1.For more info
http://www.microsoft.com/downloads/details.aspx?familyid=d20b4510-e5a6-4d7b-87a1-4bd52bdd57b8&displaylang=en

Handling Special characters in Biztalk Pipelines

2006-10-28T12:43:00.000-07:00

We had a scenario where the files have been transferred from Unix OS to Windows OS applications where each application supports different character sets. On FTP the unix box adds a special character which is invisible even in Ultra EDIT or Text Pad Editor Hex format. You might get Unexpected data found while looking for: "\r\n".
To Resolve this peculiar problem, you need to change the Code page property found in Schema level property page to ASCII format or whichever system it applies to