BizTalk Server 2010 Beta

image

I just can back from my holiday in Canada/US and noticed that BizTalk Server 2010 beta (although it can be broken or not work initially, I managed to get to the site in the end!) is available. That is cool eh (pick that up in Canada :)). It supports Windows 7; Windows Server 2008; Windows Server 2008 R2; Windows Vista.

To run BizTalk Server 2010 Beta you need:

  • 32-bit (x86) platforms: Computer with an Intel Pentium-compatible CPU that is 1 GHz or faster for single processors; 900 MHz or faster for double processors; or 700 MHz or faster for quad processors
  • 64-bit (x64) platforms: Computer with a CPU that is compatible with the AMD64 and Extended Memory 64-bit Technology (EMT64T), 1.7 GHz or faster processor recommended for BizTalk Server 2010
  • 2 GB of RAM minimum (more recommended)
  • 10 GB of available hard-disk space
  • VGA monitor (1024 x 768) or higher-resolution monitor
  • Microsoft Mouse or compatible pointing device

To use BizTalk Server 2010 Beta you need the following software:

  • Microsoft Windows: Can be Windows 7, Windows Server 2008 R2, Windows Server 2008 SP2, Windows Vista® with Service Pack 2 (SP2)
  • SQL Server 2008 R2 or SQL 2008 SP1
  • Microsoft .NET Framework 4 and .NET Framework 3.5 with Service Pack 1 (SP1)
  • Microsoft Visual Studio 2010 [Required for selected features only]
  • Microsoft Office Excel 2010 or 2007 [Required for selected features only]
  • SQL Server 2005 Notification Service [Required for selected features only]
  • SQLXML 4.0 with Service Pack 1[Required for selected features only]
  • Internet Information Services (IIS) Version 7.5 and 7.0 [Required for selected features only]

See also my previous post versions and Jean-Paul’s latest post, platforms and considerations. I decided to download the software and build a virtual machine using Hyper-V. In my latest post I discussed how to build BizTalk Virtual Machines using Hyper-V. Besides the BizTalk 2010 beta you can download:

  • BizTalkAccelerators2010_Beta.exe
  • BizTalkAdapterPack_x64_Beta.exe
  • BizTalkAdapterPack_x86_Beta.exe
  • BizTalkLOBAdapters2010_Beta.exe
  • BizTalkWCFLOBAdapterSDK_x64_Beta.exe
  • BizTalkWCFLOBAdapterSDK_x86_Beta.exe
  • Documentation on another site (contains installation/upgrade documentation).

I going to build Virtual Machine on x86 platform using Windows 2008 SP2(Centrino Duo Core, 2Gb RAM, 20 Gb Harddisk), SQL Server 2008 SP1, and Visual Studio 2010 Professional. I used the Installing BizTalk Server 2010 on Windows Server 2008 R2 and 2008 document. I installed critical updates, enabled IIS, Installed VS2010, SQL Server 2008 and applied SP1 in this order. I left out notification services 2005 , WSS, MQ and Excel 2010 installations.

I then installed the BizTalk 2010 beta and verified the installation looking in the registry reviewing this key:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\BizTalk Server\3.0

image

image

image

Configuration in my case was pretty straight forward and same as previous versions 2006, 2006 R2 and 2009.

image

My environment is setup successfully and I am ready to explore new features and try things out. I do like to note that this is a lab (experimental) setup and to setup a sustainable environment in future you need to wait for the official version and follow the installation guide (prerequisites, procedures, etcetera).

Cheers.


Technorati:

Comments

Post a Comment

Popular posts from this blog

DTAP Strategy: Pricing and Licensing

Image
To implement BizTalk solutions it is a good practice to have an DTAP environment in place. DTAP stands for Development, Test, Acceptance and Production. Development and test environments are equal (mirrored) and same account for acceptance and production. Deploying DTAP environments is easy, because there are many factors influencing outcome of DTAP. One factor is pricing and licensing costs. BizTalk is available in different editions and since BizTalk depends on operating system and database there are some configuration options to. Here is an overview of possible configurations for DTAP environments, hence there is a nice BizTalk Feature Dependency Matrix. Besides features, there are non-functional requirements to reckon with like fail-over, availability and scalability. On Microsoft Pricing and Licensing FAQ section of BizTalk I found this on non functional side. In a large BizTalk Server 2006 R2 deployment, two key considerations ensure redundancy in all areas of the architect...
Read more

BizTalk CAT Instrumentation Framework Controller: My First Experience

Image
In past I have used log4net or System.Diagnostics.Trace component of .NET for logging and tracing. Until a few months ago the post Best Practices for Instrumenting High Performance BizTalk Solutions got my attention. I read it, but did not start using it directly as I wasn’t doing any development. These days I sometimes am involved in development of BizTalk solutions, so moment was there. Recently BizTalk CAT Instrumentation Framework Controller was released on CodePlex . The BizTalk CAT Instrumentation Framework is a high performance tracing/logging framework for BizTalk that builds upon the Event Tracing for Windows (ETW) infrastructure. It was created by Microsoft's BizTalk Customer Advisory Team (CAT). The Controller is an easy-to-use GUI for the BizTalk CAT Instrumentation Framework. My thinking was why don’t I try this UI out in combination with Microsoft AppFabric CAT Best Practices Samples . The BizTalk Instrumentation Best Practices Samples solution provides a reus...
Read more

BizTalk Server 2010 Exam : How to prepare?

Image
In previous post I yesterday I wrote that new BizTalk 2010 exam is out. And you may figure how to prepare as in preparation material nothing is mentioned.Let’s look at what skills are measured. In a nutshell these topics are: Configuring messaging architecture (setup, manage ports, configure adapters, implement messaging solutions); Developing BizTalk Artefacts (building orchestrations, create schema’s, maps and pipelines); Debugging and Exception Handling (debug orchestrations, validate and test artefacts like schema’s, maps, pipelines); Integrating Web Services and Windows Communication Foundation (WCF) Services (WCF Adapters); Implementing Extended Capabilities (this is the BAM, BRE, RFID and EDI part); Deploying, Tracking, and Supporting a BizTalk Solution (Installation in different kinds of scenario’s, deployment of applications, bindings). You can find a lot of resources that can help in preparation through BizTalk Development Center like the BizTalk tutorials for EA...
Read more