none
Orchestration - Exposure through netTCP Binding RRS feed

  • Question

  • Env: BizTalk Server 2006 R2 on Windows 2003 Server

    We've built orchestration services, which were published as web services (hosted by IIS) so far, accepting http requests.

    Now we're looking at exposing the services through TCP Ports using WCF's netTCP Binding. Since all consumers apps are in Intranet and have already migrated to WCF, we want to leverage TCP communication and there by improve performance.

    a) As I understand IIS 6 ( on Windows 2003) cant be used as host, since it doesnt support tcp protocols. In this case, how should I go about it? (No plans to migrate to Windows 2008 in near future).

    b) If seperate host needs to be created for tcp, what's the methodology?     (for .net web services, its easy to create a Windows Service and make it host. Any similar mechanism here?)





    Tuesday, November 3, 2009 12:00 PM

Answers

  • Hi,

    This Windows Communication Foundation (WCF) video demonstrates using the BizTalk WCF Service Publishing Wizard.
    http://www.microsoft.com/downloads/details.aspx?FamilyID=8C1EC6A1-0ECD-4BFF-B2D8-22875ED398CE&displaylang=en

    * Supported Operating Systems: Windows Server 2003; Windows Vista; Windows XP

    or check this post: http://msdn.microsoft.com/en-us/library/bb743274%28BTS.10%29.aspx
    Sandro Pereira - http://sandroasp.spaces.live.com/blog/ http://www.devscope.net/WhatWeDo/Integration/tabid/107/Default.aspx
    • Marked as answer by sraju Saturday, November 7, 2009 3:48 PM
    Wednesday, November 4, 2009 10:10 AM
  • By the way:

    The three isolated WCF adapters (WCF-CustomIsolated, WCF-BasicHttp, and WCF-WSHttp) can be hosted on the following versions of IIS on the following operating systems:

    • IIS 5.1 on Windows XP. IIS 5.1 is designed for users developing a Web service for home or for office use. It can service only 10 simultaneous client connections, only one Web site, and it does not have all the features of the server versions. IIS replaces the Personal Web Service (PWS), which was found in earlier client versions of Windows. This environment is suitable for development deployment of the isolated WCF adapters that use HTTP communication exclusively.
    • IIS 6.0 on Windows Server 2003. IIS 6.0 provides an advanced process model that offers improved scalability, reliability, and application isolation. This environment is suitable for production deployment of the isolated WCF adapters that use HTTP communication exclusively.
    • IIS 7.0 on Windows Vista. IIS 7.0 provides the same advanced process model as IIS 6.0. The published BizTalk WCF services must run in ASP.NET Compatibility Mode of IIS 7.0.
    http://msdn.microsoft.com/en-us/library/bb226318%28BTS.10%29.aspx

    Sandro Pereira - http://sandroasp.spaces.live.com/blog/ http://www.devscope.net/WhatWeDo/Integration/tabid/107/Default.aspx
    • Marked as answer by sraju Saturday, November 7, 2009 3:48 PM
    Wednesday, November 4, 2009 10:12 AM

All replies

  • Hi,

    This Windows Communication Foundation (WCF) video demonstrates using the BizTalk WCF Service Publishing Wizard.
    http://www.microsoft.com/downloads/details.aspx?FamilyID=8C1EC6A1-0ECD-4BFF-B2D8-22875ED398CE&displaylang=en

    * Supported Operating Systems: Windows Server 2003; Windows Vista; Windows XP

    or check this post: http://msdn.microsoft.com/en-us/library/bb743274%28BTS.10%29.aspx
    Sandro Pereira - http://sandroasp.spaces.live.com/blog/ http://www.devscope.net/WhatWeDo/Integration/tabid/107/Default.aspx
    • Marked as answer by sraju Saturday, November 7, 2009 3:48 PM
    Wednesday, November 4, 2009 10:10 AM
  • By the way:

    The three isolated WCF adapters (WCF-CustomIsolated, WCF-BasicHttp, and WCF-WSHttp) can be hosted on the following versions of IIS on the following operating systems:

    • IIS 5.1 on Windows XP. IIS 5.1 is designed for users developing a Web service for home or for office use. It can service only 10 simultaneous client connections, only one Web site, and it does not have all the features of the server versions. IIS replaces the Personal Web Service (PWS), which was found in earlier client versions of Windows. This environment is suitable for development deployment of the isolated WCF adapters that use HTTP communication exclusively.
    • IIS 6.0 on Windows Server 2003. IIS 6.0 provides an advanced process model that offers improved scalability, reliability, and application isolation. This environment is suitable for production deployment of the isolated WCF adapters that use HTTP communication exclusively.
    • IIS 7.0 on Windows Vista. IIS 7.0 provides the same advanced process model as IIS 6.0. The published BizTalk WCF services must run in ASP.NET Compatibility Mode of IIS 7.0.
    http://msdn.microsoft.com/en-us/library/bb226318%28BTS.10%29.aspx

    Sandro Pereira - http://sandroasp.spaces.live.com/blog/ http://www.devscope.net/WhatWeDo/Integration/tabid/107/Default.aspx
    • Marked as answer by sraju Saturday, November 7, 2009 3:48 PM
    Wednesday, November 4, 2009 10:12 AM
  • Hi,

    As far as hosting is concerned WAS (Windows Activation Service) could be used instead of plain windows service I believe because you are anyway using IIS 6 or IIS 7.

    You can also host it inside a console application with infinite while loop and make it run everytime you log in by writing following code in program.cs :

    using Microsoft.Win32;
    ...
    ...

    RegistryKey rkApp = Registry.LocalMachine.OpenSubKey(@"SOFTWARE\MICROSOFT\WINDOWS\CURRENTVERSION\RUN", true);
    rkApp.SetValue("<your console application name>", Application.ExecutablePath);

    Thus, everytime you log on the console application would start and keep running thereby hosting the WCF service.

    Despite everything, using WAS is the better option.

     


    Please mark as answer if this helps you. Thanks and warm regards Ambar Ray EAI Architect - Microsoft Technologies
    • Proposed as answer by Ambar Ray Friday, November 6, 2009 5:38 AM
    Friday, November 6, 2009 5:38 AM