<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>biztalk on Ralph Romero</title>
    <link>https://blog.romero.id.au/tags/biztalk/</link>
    <description>Recent content in biztalk on Ralph Romero</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Fri, 11 Dec 2020 00:00:00 +0000</lastBuildDate><atom:link href="https://blog.romero.id.au/tags/biztalk/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Adding Custom WCF Headers Outbound from Biztalk</title>
      <link>https://blog.romero.id.au/posts/addingcustomwcfheadersbiztalk/</link>
      <pubDate>Fri, 11 Dec 2020 00:00:00 +0000</pubDate>
      
      <guid>https://blog.romero.id.au/posts/addingcustomwcfheadersbiztalk/</guid>
      <description>You may have written a WCF client calling a SOAP service with some custom headers and are wondering how to the same thing in Biztalk. I&amp;rsquo;ll explain how to map what you would do in C# with how to implement it in Biztalk.
Starting with a sample C# client
var xmlns = &amp;#34;http://www.myns.com&amp;#34;; var usn = &amp;#34;myusername&amp;#34;; var pw = &amp;#34;mypassword&amp;#34;; var userHeader = MessageHeader.CreateHeader(&amp;#34;Username&amp;#34;, ns: xmlns, value: usn); var pwHeader = MessageHeader.</description>
    </item>
    
    <item>
      <title>Serving a Static Website from Biztalk</title>
      <link>https://blog.romero.id.au/posts/servingstaticwebsitefrombiztalk/</link>
      <pubDate>Mon, 15 Jun 2020 00:00:00 +0000</pubDate>
      
      <guid>https://blog.romero.id.au/posts/servingstaticwebsitefrombiztalk/</guid>
      <description>It is possible for Biztalk server to act directly as a basic web server serving up dynamic content. Of course you should consider when you need a full featured web server, but for basic cases such as serving up information to internal users, this can be a really simple solution.
The following shows how this is implemented.
Create Receive Location Create a WCF-WebHttp request response receive location. Pipelines should be set to passthrough.</description>
    </item>
    
  </channel>
</rss>
