In some real-life scenarios, deploy ing several BizTalk schemas on the same box, as a schema versioning solution or not, can cause multiple identical message types with the same namespace and root element name. Due to same exact message schema deployed twice (or more) or different schemas for different messages, but with the same root element and namespace. The known error that pops out when naively executing the scenario described is as followed: Event Type: Error Event Source: BizTalk Server 2006...
Most "hello world" sample of generating & consuming Web-Services starts with simple method that passes string parameters between the service provider & consumer. Somehow, the approach for the very same sample get complex in BizTalk world. Our aim is to consume the "hello world" web service method that as I mentioned before has a string input parameter. The real question is what message formation we should send to the SOAP send port so that the SOAP adapter comprehend that...
It's been a while I'm trying to understand how to perform a Delivery Notification on a BizTalk Direct Logical Send Port. All the samples and the posts around the issue never mentioned sending the message directly into the MsgBox. They all talked about the guidance of performing the ACK/NACK on a Specify Later, Specify Now or Dynamic port configuration - not Direct. Well here is how I did it on a Direct style: 1. Assuming the message I'm trying to send (and check for delivery) is called...