Azure Thoughts, EAI Challenges

Before end of the year a new issue of BizTalk Hotrod is made available . I happy to announce that my article around BizTalk Adapter Pack 2.0 is in this issue. Some of you know that I posted a few things around BizTalk Adapter Pack in August . This inspired me to write an article and share my experience/knowledge with fellow BizTalk professionals in the world. Information shared was a bit more than you put in a blog post. Alongside my article you will find articles about ESB Toolkit, BAM, HL7, Management with Powershell from fellow Dutch BizTalk pro Randal van Splunteren and all, Creating Custom Receive Decoder Pipeline and Business Process Automation with SharePoint and BizTalk. Enjoy reading the magazine. Technorati: BizTalk BizTalk 2006 R2 BizTalk Server 2009

Monitoring Scenario In this post and the next I would like to go through a scenario to have the ability to further evaluate the three monitoring tools for BizTalk. I will use an Oracle backend (i.e. Oracle 10g Express), .NET, BizTalk and a Windows Front End application. I have an environment (VPC) that contains BizTalk Adapter Pack 2.0, Oracle Express 10g, BizTalk Server 2009 and the three monitoring tools BizMon, Minotaur and FRENDS Helium. In this scenario we will expose data inside Oracle database to an application and update this information to our liking and see to it that it will be updated in Oracle database. BizTalk (Messaging) together with Adapter Pack 2.0 (Connectivity) will be exposing the Oracle through messages, by submitting a request and receiving a response. Update to data be routed back through update request and response will be shown in front end application. Below you will find a diagram to visualize the process (scenario) just described. We will use the three mo

In previous posts ( part 1 , part 2 ) I mentioned three tools for monitoring BizTalk solution, BizMon, Minotaur and FRENDS Helium. In this post I want to dive into installation, configuration of FRENDS Helium . This is a web-based tool for monitoring BizTalk Server installations and provides operators a simple view to error situations occurred in BizTalk Server installation. You obtain a trail version through their website . You will be provided with license key instantly and url to download trail. Note that you have to give your details by registering yourself. If you fail to do so you will be presented by following message: License error Sorry, the license could not be verified: Loading license failed: Could not find file 'C:\Program Files\Frends Technology\FRENDS Helium\FrendsHelium.lic'. Please contact your friendly administrator, he should be able to fix the license problem. Installation on my VPC was pretty straight forward, but I did run into determining disk problem a

In previous post ( part 1 ) I mentioned three tools for monitoring BizTalk solution, BizMon, Minotaur and FRENDS Helium. In this post I want to dive into installation, configuration of Minotaur V1.04 monitoring tool. I use same environment as for BizMon tool. Minotaur is licensed per BizTalk group, so after installation you will to ask for a license key by sending an email to Registration@RagingBullTech.com with following details: SQL Server Name \ Instance Name and BizTalk Management database name. When you want to install Minotaur on Windows 2008 as in my environment it has to be done under a local administrator account. This account also needs to be member of BizTalk Administration group and in my case since I am using IIS 7.0 also member of IIS_IUSRS group. During installation three components can be installed: After features page you will be presented with the SQL Information page, the Connection String page and the Service Credentials page. For service crendentials I created