<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.msdn.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Advanced BizTalk 2006 Web Services, Part II</title><link>http://blogs.msdn.com/richardbpi/archive/2006/10/23/advanced-biztalk-2006-web-services-part-ii.aspx</link><description>In Part I of this two post series, I began a look at some advanced concepts around BizTalk-generated web services. In this post, we look at two additional concepts. In the last post , I demonstrated the following topics ... Using the "bare" and "wrapped"</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>Richard Seroter - SoCal BizTalk Musings : Advanced BizTalk 2006 Web Services, Part I</title><link>http://blogs.msdn.com/richardbpi/archive/2006/10/23/advanced-biztalk-2006-web-services-part-ii.aspx#863778</link><pubDate>Mon, 23 Oct 2006 20:24:31 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:863778</guid><dc:creator>Richard Seroter - SoCal BizTalk Musings : Advanced BizTalk 2006 Web Services, Part I</dc:creator><description>&lt;p&gt;PingBack from &lt;a rel="nofollow" target="_new" href="http://blogs.msdn.com/richardbpi/archive/2006/10/23/advanced-biztalk-2006-web-services-part-i.aspx"&gt;http://blogs.msdn.com/richardbpi/archive/2006/10/23/advanced-biztalk-2006-web-services-part-i.aspx&lt;/a&gt;&lt;/p&gt;
</description></item><item><title>re: Advanced BizTalk 2006 Web Services, Part II</title><link>http://blogs.msdn.com/richardbpi/archive/2006/10/23/advanced-biztalk-2006-web-services-part-ii.aspx#864276</link><pubDate>Mon, 23 Oct 2006 20:56:08 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:864276</guid><dc:creator>Kris</dc:creator><description>&lt;p&gt;Very informative. We are using Biztalk in an intranet scenario and are planning to make use of it in our internet application too. &lt;/p&gt;
&lt;p&gt;Is it possible to host Biztalk Webservices on a host other then the Biztalk server itself. In other words do you need to have a Biztalk instance on the server where the webservices are hosted to connect to the Biztalk server? I couldn't find much information with regard to the same. Can you please clarify.&lt;/p&gt;
&lt;p&gt;Thanks.&lt;/p&gt;</description></item><item><title>re: Advanced BizTalk 2006 Web Services, Part II</title><link>http://blogs.msdn.com/richardbpi/archive/2006/10/23/advanced-biztalk-2006-web-services-part-ii.aspx#864882</link><pubDate>Mon, 23 Oct 2006 21:44:53 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:864882</guid><dc:creator>rseroter</dc:creator><description>&lt;p&gt;Hey Kris,&lt;/p&gt;
&lt;p&gt;Yes, BizTalk Server sits on the box(es) with IIS. &amp;nbsp;Ideally, you're running only the SOAP host instance on that box, with limited user rights. &amp;nbsp;Then when services are published to the SOAP end point, the BizTalk Isolated Host instance can grab the inbound message and publish into the MessageBox.&lt;/p&gt;
</description></item><item><title>re: Advanced BizTalk 2006 Web Services, Part II</title><link>http://blogs.msdn.com/richardbpi/archive/2006/10/23/advanced-biztalk-2006-web-services-part-ii.aspx#865288</link><pubDate>Mon, 23 Oct 2006 23:16:31 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:865288</guid><dc:creator>Kris</dc:creator><description>&lt;p&gt;Thanks for the info. Is this going to change in the future R2 or vNext? I ask this because the IT folks are reluctant to install any new server software on external facing IIS machines because they believe it exposes the surface area of attack. Do you hear this issue often? Wouldn't it be possible to have a generic webservice for the Biztalk server that could publish the message directly to the message box.&lt;/p&gt;</description></item><item><title>re: Advanced BizTalk 2006 Web Services, Part II</title><link>http://blogs.msdn.com/richardbpi/archive/2006/10/23/advanced-biztalk-2006-web-services-part-ii.aspx#865457</link><pubDate>Mon, 23 Oct 2006 23:35:08 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:865457</guid><dc:creator>rseroter</dc:creator><description>&lt;p&gt;R2 won't be any different, and it's too early to say on vNext. &amp;nbsp;BizTalk shouldn't be placed on any external facing machines, rather, you should be using a reverse proxy (see &lt;a rel="nofollow" target="_new" href="http://www.microsoft.com/technet/isa/2004/plan/bestpractices.mspx"&gt;http://www.microsoft.com/technet/isa/2004/plan/bestpractices.mspx&lt;/a&gt; , search for reverse proxy). &amp;nbsp; So BizTalk sits behind the firewall, and traffic filtered from external facing IIS servers. &amp;nbsp;&lt;/p&gt;
</description></item><item><title>re: Advanced BizTalk 2006 Web Services, Part II</title><link>http://blogs.msdn.com/richardbpi/archive/2006/10/23/advanced-biztalk-2006-web-services-part-ii.aspx#1056874</link><pubDate>Sat, 11 Nov 2006 05:24:25 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:1056874</guid><dc:creator>Tom</dc:creator><description>&lt;p&gt;Another option would be to deploy a stand-alone .net web service externally &amp;amp; tunnel back with msmq (over http), etc.&lt;/p&gt;</description></item></channel></rss>