When working with BizTalk Server EDI, configuring the correlation between the Send Ports and the Party/Agreements might sometimes require more flexibility than the Agreement set up provides us…
We will now look at the differences and similarities of the old SQL Adapter vs. the new WCF SQL Adapter when it comes to sending from BizTalk; both doing one-way and solicit-response communication with the SQL Server.
Migrating to WCF SQL Adapter from SQL Adapter (Receiving) When migrating from the old deprecated SQL Adapter in BizTalk Server to the new WCF SQL Adapter, there are a few things to take into consideration. This article will try to explain how to do a one-to-one migration most painless and also discuss if such a migration is the best option. […]
Background XML sent from BizTalk through a Send Port will, per default, always be encoded as UTF-8. When XML is encoded as UTF-8 no encoding and XML declaration is needed, so if using a PassThruTransmit Pipeline, the XML output will be UTF-8 with no declaration: Shown in Internet Explorer like this:
Over the last 3 years I’ve started using custom XSLT to a greater extent than previously. Today, my default choice of option is undoubtedly custom XSLT, and I demand very convincing arguments, such as “business employees without any developer skills are responsible for creating a lot of very simple mappings”, before I recommend dragging Functoids to the grid.