24 Apr

BizTalk, WIF, WF Tutorial – Part 1.1 Setting up the environment – operating system.

There’s a variety of systems to chose from when we analysis BizTalk Server 2010 Server requirements. There’s even Windows 7 to choose from. The problem is, when we want to have the environment the closest to the production one, we should use any of the available Windows Servers. I decided to choose the one I am already familiar with, that is Windows Server 2008 R2. It’s available free of charge on Microsoft Websites as 180 days evaluation version. Enough to suit our needs.

I am definitely not going to describe how to install an operating system. That should the intelligent reader do on their own. I strongly recommend giving VDISKs a try. That’s a relatively new feature allowing to create Virtual Hard Drives, completely reusable, for example in Hyper-V. In my case, I had to resort to installing completely independent operating system not using any of the virtualisation tools, because my Intel Core Duo 2 is not yet prone to 64bit virtualisation capabilities. But still, VDSIK came in handy , not forcing any physical disk partitioning.

Once we have our fresh servers installed, we proceed to install:

  • Web Server Role (complete)
  • Features that can make our life easier, e.g. Windows Desktop Experience, Wireless Lan  Service.

For now that’s all we need to have. We continue our journey in Part 1.2.

24 Apr

BizTalk 2010 & Windows Identity Foundation (AD FS 2.0 & StarterSTS) & Worflow Foundation & more and more

On my old blog, before I have lost all the date from the former server, I promised myself an all the readers, who devoted their time to follow my notes, that the time would come, when I write everything I know about putting Federated Security between BizTalk, Workflow Foundation using the AD FS 2.0, StarterSTS to work in SOA architecture. Me and my friend Kacper Oko have already succeeded to do so in our master thesis. Now it’s the time to give back what we’ve taken from the thousands blog post, forum posts which helped us in achieving our goal. I’ll try to describe step by step and from the scratch how to start playing with BizTalk and all other mentioned technolgoies. Already in? See Part 1.

15 Jan

BizTalk: Receive Location (Isolated) on IIS Server and big messages

Whenever we’re trying to create an isolated Receive Location hosten in IIS we need to answer the question: How big messages should accept our WebService (classic or WCF). If we’re trying to receive messages with images or documents, we need to assure that our service is ready to accept those request. Otherwise our clients can receive instead of a confirmation, some error message that not always says anything about the configuration.

In order to adjust the request size we need to open Internet Information Services Manager. After selecting the application corresponding our WebService, we click on Configuration Editor.

IIS Server Manager - Configuration Editor

What we look for is the option httpRuntime.

IIS Manager - Configuration - httpRuntime

In the end, we look for maxRequestLength and set it to the value that suits our requirements. In my case it was the maximal allowed value: 2147483647



22 Oct

BizTalk and WIF: Receive location and port

As I promised a log time ago, I’ll try to describe in a few notes how I managed to federate BizTalk Server 2010 with StarterSTS and of course ADFS 2.0. One of the most important parts was forcing BizTalk to respect custom configuration files with proper bindings. It took me quite a while. But let’s make it step by step.

In order to start the orchestration that was responsible for the business process that I’ve automated, I needed a trigger. An orchestration is in BizTalk always triggered by the incoming message of the particular type. Exactly the same was in the one of my own. Therefore the situation was more interesting. Due to the SOA Paradigm I was using, I wanted to publish the orchestration as a WebService. This is of course possible in BizTalk. Moreover there are two options. ASP.NET WebService and WCF WebService. Knowing that my service needs to support the newest ws2007FederationHttpBinding that comes with Windows Identity Foundation, I used always the creator for WCF service.

Waht the most important is that in BizTalk 2010 the services can use two availible adapters:

  • the default one
  • Isolated adapter.

At the beginning I thought that it makes no difference which one I chose. But when I tried to modify the web.config published in the IIS by the creator, no changes were respected. As it turned out to be, the default adapter was hosted by BizTalk itself. Therefore the configuration corresponding to the web.config was stored somewhere else. And in the place not particularly available. The problem was that I needed to change the default settings and use the proper binding required by WIF.

As it turned out to be  changing the receive location to Isolated adapter (this means: the service is 100% IIS service and there installed & configured) resolved the problem. With these settings the web.config file could be aligned to the requirements. The configuration was now respected and federating BizTalk using ADFS  2.0 worked like a charm.

22 Oct

Here we go again…

The previous server has gone down. I purchased another one but unfortunately until now I haven’t enough time to setup the blog. Finally the time has come… We start again. I hope with regular posting. I hope you’ll enjoy reading as much as I enjoy posting!