Posts

Showing posts from January, 2010

Benchmark my VPC

Image
My colleague Gijs (BizTalk MVP) pointed me towards benchmark tool for BizTalk. This wizard checks the performance of your BizTalk Server installation using pre-existing scenarios and validates it against some known results. I thought I will give it a spin on my VPC (sandbox BizTalk 2009 environment with SQL Server 2008 Enterprise and Windows 2008 Enterprise). Installation process is describe on this blogpost . Run script: If follow up the rest of process and you have your Benchmark tool set to go. Start Wizard, give correct database name, let check prerequisites and select a scenario: In this case a Single Server Installation with orchestration with singel messagebox. Fill in details (server name, test duration), start Indigo service.   Test service: Run the test: and then finally the results as test is running: This test runned inside my VPC, with 1024 Mb memory and 1 CPU (Centrino Vpro Dual Core). Test did succeed completly: I finished

Microsoft Hotfix BizTalk Server 2009/VS 2008

Image
I am currently quite active on BizTalk forums and must say it is a great experience for me helping out people in field. It gives me great satisfaction to be able to share some of experience and knowlegde around BizTalk Server and integration. You see some people having difficulties around VS 2008 and BizTalk Server 2009: like broken schema references . There is a hotfix out that will, I quote: “On a computer that is running Microsoft BizTalk Server 2009, you use Microsoft Visual Studio to develop a BizTalk application. In your BizTalk project, you add a reference to another BizTalk project. In this scenario, you may see the following behavior: The orchestrations in the referenced BizTalk project may show compiler warnings. The changes that are made to the referenced BizTalk project are not propagated on to the referencing project. When you edit the orchestrations of the referenced project, XLANG errors are thrown. These errors may disappear after the orchestrations are

BizTalk and MSDTC

Image
Microsoft Distributed Transaction Coordinator (MSDTC) is an important component in a BizTalk environment. Especially in multi-server environment it is mandatory and needs to setup and configured properly before one starts configuring BizTalk features like group, BRE or BAM. During configuration of these BizTalk features, databases like BizTalkMsgBoxDb, BizTalkMgmtDb, BizTalkDTADb (tracking archiving), BizTalkRuleEngineDb, or BAMPrimairyImport and other (BAMStar, ect) are created on database server. MSDTC is component inside Component Services (Windows 2003, Windows 2008). Below is a screen from DTC inside Component Services Windows Server 2008.   By right clicking Local DTC you can configure it via three tabs (Tracing, Logging, and Security). To enable MSDTC on Windows Server 2003 or 2008 you can find that on this MSDN page . Below is a screen from DTC inside Component Services Windows Server 2003. There are three tabs available and first on is Tracing (this accounts W2K8):

BizTalk Server 2006 R2 Exam

Image
I like to wish you all a happy new year to start with. Before end of 2009 I passed the 70-241 BizTalk exam. This exam has been around for quite a while and I kept postponing to take it for a long time, but I finally decided to take it. So now my logo looks like this (maybe not exciting and many of you may have similar logo’s but still I am proud to have achieved this):   As soon as there will be an exam for BizTalk 2009 I will take sooner and not wait for ever :).