SOA Conference …

A few people from the BizTalk Adapter Pack and the WCF LOB Adapter SDK are going to be attending the SOA-BP conference at Redmond (Oct 29th – Nov 2nd). If you have any questions, feel free to contact us there. At present, I have no idea where exactly we will be available at during the conference sessions, but you can leave a comment here (on this post), and we’ll set up a time when we can meet with you.

Comments (4)

  1. bdavidwilliams says:


    I have finished the EchoAdapterSampleV2 tutorial ( ).  It was quite good.

    I also was able to consume the adapter from a ConsoleApplication.

    I have also downloaded and studied JR’s SQLSampleAdapter (see attached in  I have read some of

    I have created my own adapter.  It’s quite simple so far.  I did not implement interfaces IMetadataBrowseHandler, IMetadataResolverHandler, nor IMetadataSearchHandler.  I did implement IInboundHandler (and will later implement IOutboundHandler).

    I do not think I have to implement those metadata interfaces, in order to get this WCF LOB custom adapter working in receive location/ports and/or send ports, right?

    But what I can’t find, is:

    1.) How do I now get a BizTalk 2006 R2 rcv location/port configured to make use of my WCF LOB custom adapter (it has custom properties, which will enable connection to the LOB system

    2.) When I do have the receive location/port set up to use my custom WCF LOB adapter, what method within MyAdapterInboundHandler.cs will be called (by the BizTalk 2006 R2 rcv location/port runtime) ?

  2. Point 1 – Create a Receive Port, choose the Adapter as WCF-Custom, and then in the configuration, on one of the tabs, you can choose your binding.

    Point 2 – You need to implement all the methods in the InboundHandler abstract class – all of them will be required at runtime.

  3. bdavidwilliams says:

    Thank you, that helped a lot.

    I now have my WCF-Custom adapter configured in a receive location in BizTalk 2006 R2.  I have it configured as "WCF-Custom" (and not "WCF-CustomIsolated").

    I have code for all methods in MyAdapterInboundHandler (implementing MyAdapterHandlerBase, IInboundHandler)

    and then in the WCF-Custom Transport Properties window, in the ‘Messages’ tab, in the ‘Error handling’ section (near bottom),

    I have the ‘Include exception detail in faults’ checked;  I have, in the ‘Behavior’ tab, under the ‘Behavior –> ServiceBehavior –> serviceDebug’ … under ‘Configuration’ -> includeExceptionDetailInFaults set to True

    So in Windows Event Viewer, I’m seeing:

    Error   Event ID: 5644
    and then I see a stack trace with an error.

    So I want to see the tracing.  I have lots of stuff like this in the code:

    MyAdapterUtilities.Trace.Trace(System.Diagnostics.TraceEventType.Information, "MyAdapterConnection::ctor", "Connection connectionString is: " + connectionString);

    So then I followed (and modified C:Program FilesMicrosoft BizTalk Server 2006BTSNTSvc.exe.config accordingly)

    and I get the c:logsmessages.svclog  when I stop and restart the BizTalk service ….

    But then I see nothing, when using the Service Trace Viewer, about MyAdapter ….

    By the way, did you see my ‘Wednesday, December 05, 2007 2:38 PM’ question at ?  I know it’s not your code, but can you take a look at that line 56 of the SQLAdapterOutboundHandler.cs (from the attached in that original blog entry) and tell me what your best guestimate in completing that incomplete line of code is…

  4. I would say that you need to ensure the following:

    (a) The trace names match. (the trace name is not always the same as your dll name – it depends on what your code says the name is)

    (b) Ensure that the trace listener is correctly set up, writing to the correct file, etc.

    (c) In the statements which you trace out, ensure that the Description field is not null.

    You can open the messages.svclog in notepad, and do a quick search to see whether your trace statements are actually there in the log or not.