Making a BT2006/R2 orch published as .asmx backward comaptible with BT2004

Home Page › Forums › BizTalk 2004 – BizTalk 2010 › Making a BT2006/R2 orch published as .asmx backward comaptible with BT2004

Viewing 2 reply threads
  • Author
    Posts
    • #20058

       We are rewriting a system with BT2004 orch published as a .asmx web service.

      In BT2006/R2 I published my orchestration in the same manner, with same schemas.

      I wrote a C# to run against the BT2004, and it works.  My goal is just to change the URL and have it still work.
      In other words, we don’t want our vendor to have to change anything. 

      The old one has a service name like this:

        <wsdl:service name=”ImagingInterfaceLoanDataPull”>
       

      The new BT2006 has a service name like this:

        <wsdl:service name=”TMAC_AdfiTech_BizTalk_Orchestrations_orchDataPull_otpLoanDataPull”>

      So how does it decide what the service names are?
      I already changed the Operation_1 on the logical ports to match.

      There are also some minor differences in how it built the complex-types in the WSDL, but I think the above is my first issue.

      Thanks,
      Neal Walters

    • #20059

       Here’s one quick clarification: otpLoanDataPull was my interanal PortName, which I can change to ImagingInterfaceLoanDataPull.  But BT2006/R2 seems to prefix it with the full namespace TMAC_Adfitech etc…  Is there way not to prefix it with the namespace?

      Neal

    • #20060

      Can you just move the web service files from the BizTalk 2004 box to the BizTalk 2006 box, instead of re-publishing it?  I would try this first.

      • #20061

         If there are any orchestration/port name discrepencies, it should be fairly simple to open the web service files and update the web update them with the correct names.

        • #20063

          1)  Can you just move the web service files from the BizTalk 2004 box to the BizTalk 2006 box, instead of re-publishing it?  I would try this first.

             Not sure what you mean here.  You mean just overlay the BT2006 WSDL with the BT2004 WSDL? 

           2) If there are any orchestration/port name discrepencies, it should be fairly simple to open the web service files and update the web update them with the correct names.

              Ah, I keep forgetting that .asmx create a C# solution and source code (where as WCF publish does not).  I’ll take a look there.

          Thanks,
          Neal

          • #20064

            By moving the web service files, I mean moving the whole C# solution from the old server to the new server.  You will probably need to manually recreate the virtual directory in IIS on the new server.  Then you can just move over the receive ports by exporting bidings.

Viewing 2 reply threads
  • The forum ‘BizTalk 2004 – BizTalk 2010’ is closed to new topics and replies.