This one starts with a joke:
A gentleman walks up to a wall and starts banging his head against it. Hard. In fact, he bangs his head so hard, that people around grow concerned and one person says to him, “Sir, why do you keep banging your head against the wall?” He replies, “Because it feels so good when I stop.”
So, like the gentleman in the above joke, I’ve been (figuratively) banging my head against the wall while trying to figure out how to invoke a Logic App I have deployed to the Azure cloud via an HttpListener.
I was using a
PostAsync() call on the
HttpClient to invoke the listener, but kept getting a
405 - Method Not Supported exception from the service. I was pretty sure POST should have been allowed! After checking the address, double-checking all the configurations, and so forth I couldn’t figure out why I would get the response I got (hence, the figurative banging of my head against a wall).
As is often the case, I found the answer in a post on an MSDN forum. When I copied the URL from the API definition of my HttpListener in Azure, it began with
http instead of
https, which was required. A simple mistake and easy to miss.
After making the URL correction, adding an “s” to
http, my calls to the service worked just fine.
And it feels really good now that I’ve stopped banging my head against the wall.
Just recently I presented “Getting Started with Microsoft Azure API Management” at TechFuse 2015 at the Minneapolis Convention Center. Thanks to all those who attended! For those who may just be interested, you may find my PowerPoint slides from the presentation here
I’m proud to announce that I’ve been selected as a speaker at TechFuse 2015! The conference takes place at the Minneapolis Convention Center on April 21, 2015. I’ll be presenting “Getting Started with Microsoft Azure API Management” in the Development track. As usual, presentation slides and sample code will be available on this site sometime after the conference. If you’ve got a day to take in some awesome tech content, come by and check it out! More info is available here: http://www.techfusemn.com/
The reports of my death have been greatly exaggerated.
-Microsoft BizTalk Server*
*also Mark Twain who was quite alive at the time he said this…
Over the last few years, rumors have been swirling around the BizTalk community regarding the life (or impending death) of BizTalk server. At Tech-Ed 2012 and the BizTalk Summit in December, Microsoft finally put those rumors to rest. Now BizTalk 2013 is more than just on the horizon, it’s available in RTM!
Here’s a quick list of what we’re getting with this release…
- Platform Updates (Visual Studio 2012, Windows Server 2012, SQL Server 2012, Office 2013, System Center 2012)
- Updated EDI and HL7
- Updated LOB Adapters for SAP, Oracle, and Siebel
- The ability to associate a host other than the default for dynamic send ports
- Improved performance for ordered send ports
- XslCompiledTransforms in maps
- Ability to view artifact dependencies (BIG win, here)
- REST Support (another HUGE win)
- Easier installation and configuration of the ESB Toolkit
- Connectivity to Azure Service Bus and Storage
And one of the coolest things… BizTalk IN THE CLOUD! Besides the capability for adding BizTalk in a VM, BizTalk also will be available as part of the Azure “fabric” and will be integrated with the Azure management portal.
So lots of exciting stuff coming out. Pay attention, it’ll all be available soon! In the meantime, MSDN subscribers can access the RTM bits for BizTalk 2013 On-Premise right away!
UPDATE: (2013-May-5) Since I first published this, Microsoft has released a “trial edition” VM that you may use on Azure that uses only your regular compute hour allotment. We’re happy again!
I’m sorry I promoted this yesterday without understanding the billing model. Using BizTalk Enterprise VM in Azure with your MSDN subscription does not use just the normal compute hours that comes with the subscription. Using BizTalk within an Azure VM has a separate compute time charge and as of yet, there are no free hours with it. My own Azure account was disabled because of the $0.00 limit for charges I have on my account.
I’ll keep you posted should this change. I apologize for any heart-ache this may have caused!