Screencast: BizTalk WCF Adapters -- Send Port Basics

Excellent screen cast.

Unfortunately I can't get this to work.

One of the things I don't get is how to the security mode should be configured. Default it is Message. But when I set up Message on the server side also, I get an error in WCF tracelog telling me:

No signature message parts were specified for messages with the 'localhost/.../MyOperation2& action.

When I set both BizTalk and server to security mode = None I get:

The message with Action 'localhost/.../MyOperation2& cannot be processed at the receiver, due to a ContractFilter mismatch at the EndpointDispatcher. This may be because of either a contract mismatch (mismatched Actions between sender and receiver) or a binding/security mismatch between the sender and the receiver.  Check that sender and receiver have the same contract and the same binding (including security requirements, e.g. Message, Transport, None).

I like to know how you did set up your server.

Is it possible for you to publish your solution somewhere?

Thanks,

René Titulaer

Hi,

this article is excellent. Unfortunately it still took me two days to get a BizTalk WCF send port to work.

First thing which really helped me was the import functionality of a WCF custom adapter.

I couldn't get the send port to work manually (by setting up a WCF adapter for wsHttp). Import did the job (by importing the app.config of a WCF test client).

Another thing which took me a day to solve was the requirement that the WCF service should have a contract of type MessageContract instead of DataContract (and IsWrapped should be set to false). I don't understand why this isn't mentioned explicitly in this document because DataContract is the standard. Everyone will run into the problem that the soap body which BizTalk sends is different then the soap body expected by the default WCF service (because BizTalk doesn't create a root element for the operation name of the soap method).

Thanks,

René Titulaer

rene.titulaer@oce.com