Поделиться через

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

  • Anonymous
    December 06, 2007
    Hello,I have finished the EchoAdapterSampleV2 tutorial ( http://technet.microsoft.com/en-us/library/bb798134.aspx ).  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 Demos.zip attached in http://weblogs.asp.net/gsusx/archive/2007/11/05/demos-from-the-microsoft-soa-amp-bpm-conference.aspx).  I have read some of http://www.pluralsight.com/blogs/aaronI 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 system2.) 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) ?
  • Anonymous
    December 07, 2007
    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.
  • Anonymous
    December 11, 2007
    The comment has been removed
  • Anonymous
    December 14, 2007
    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.