Finally, BizTalk Server 2009 supports the latest Microsoft application platform technologies, including Windows Server 2008, Microsoft Visual Studio 2008 SP1, Microsoft SQL Server 2008 and the .NET Framework 3.5 SP1. BizTalk Server 2009 also delivers expanded new connectivity options including new integration with Oracle e-Business Suite, as well as updated platform support for the most recent versions of IBM Customer Information Control System (CICS), Information Management System (IMS), DB2, DB2/400, DB2 Universal Database and WebSphere MQ. You can download BizTalk 2009 Beta Evaluation version at Connect.Microsoft.com.
BizTalk Server 2009 delivers improved scalability and reliability through support for SQL Server 2008, Windows Server 2008 Hyper-V virtualization and enhanced failover clustering. It also provides significant new enhancements to both individual and team productivity by enabling new interoperability with ALM solution: Visual Studio Team System and Team Foundation Server 2008. This allows development teams to utilize the integrated source control, bug tracking, team development support, Project Server integration, and support for automating builds via MSBuild for a more seamless development and testing experience.
In this post, I will guide you to install BizTalk 2009 Beta and start working with it using Visual Studio 2008. First, you have to download BizTalk 2009 with its components (UDDI services, adapter pack, accelerator) from connect website. Before you download and install BizTalk 2009, I assumed you already have the following in your machine:
- OS : Win Svr 2008, or Vista SP1 with all critical updates.
- IIS : IIS 7.0
- VS 2008 SP1: Install C# or VB.NET
- SQL 2008 : Default installation. SQL 2005 is also applicable.
- Sharepoint : WSS 3.0 SP1 or MOSS 2007 SP1
I am using Windows Server 2008 x-64 with VS 2008, SQL 2008 and MOSS 2007 installed.
Install BizTalk 2009
After installed IIS, VS 2008, SQL 2008 and Sharepoint (WSS/MOSS), you are ready to install BizTalk 2009. Remember that you also have to install BizTalk Redistribution Pack (download links for pre-downloaded CAB are listed in BizTalk 2009 installation guide) if some pre-requisites are not installed in your machine.
In my case I installed all the BizTalk core components for single server installation including BAM, Dev Tools and SDK, Documentations, Server runtime and additional software. If everything ok with your installation, you can launch the BizTalk Server configuration wizard. But before we configure BizTalk, something need to be done.
When using the SQL Server shared memory protocol with BizTalk Server 2009 you might experience degradation in performance under certain stress conditions, if clients are accessing SQL Server from the same computer. To resolve the problem you need to disable the use of the shared memory network protocol in the SQL Server Client Network Utility. After you disable the shared memory protocol, you will need to restart SQL Server services.
Configure BizTalk 2009
In this task, I will show you how to configure BizTalk Server 2009 using the Basic configuration option. Basic configuration is recommended for developers setting up a complete installation of BizTalk Server running on a single server. When configuring BizTalk Server 2009 using basic configuration, consider the following:
- Configuring a remote SQL Server is not supported.
- Configuring against SQL Server 2008 default instances and named instances is supported.
- Account you are logged on is local administrators and have System Administrator rights on SQL Server.
- The account you are logged on must be a member of the OLAP Administrators on the OLAP box if configuring.
- You cannot configure BAM Analysis on a SQL Server named instance using basic configuration.
When you use the basic configuration option, the following occurs:
- All database names are generated by BizTalk Server.
- All applicable database logon information is run under the account provided.
- All BizTalk Server services are generated by BizTalk Server.
- All BizTalk Server services run under the account provided.
- All features are configured based on the prerequisite software you have installed on the computer.
- The logged on user must be a member of the OLAP Administrators group on the OLAP server.
- The Default Web Site in Internet Information Services (IIS) is used for any feature that requires IIS.
The implication of the last point is we need to extend Default Website as a virtual server. WSS/MOSS uses virtual servers to host Web sites on server. The process of applying WSS/MOSS to a virtual server is called extending. We must extend a virtual server with WSS/MOSS before we can create a Web site based on WSS. We can do that in MOSS with the following steps:
- Go to Microsoft WSS/MOSS Central Administration.
- Navigate to the Application Management page.
- Under SharePoint Web Application Management, select Create or Extend Web Application.
- On the Create or Extend Web Application page, select Extend an existing Web application.
- On the Extend Web Application to Another IIS Web Site page, Select Change Web Application.
- On the Select Web Application page, select SharePoint Central Administration 3.0, and then click OK.
- In the IIS Web Site section, click Use an existing IIS Web site.
- Select Default Web Site.
- Leave the rest of the default values, and then click OK.
Work with Visual Studio 2008
BizTalk 2009 is fully integrated to Visual Studio 2008. To start with BizTalk project, you can open Visual Studio 2008 and create BizTalk empty project. All BizTalk project (Schema, Map, Pipeline, and Orchestration) will be compiled as .NET Assembly (DLL).
I will not discuss about BizTalk development here, only to give you starting point on BizTalk 2009 and Visual Studio 2008. BizTalk Development tools provides Visual Studio templates and visual designers to enable developer working on schemas, mapping the schemas, and doing system workflow (orchestration) and defining send/receive pipelines.
Visual designers in BizTalk are just tools to make your life easier when dealing with the BizTalk APIs.
We will discuss more about BizTalk development in my incoming postings.
Stay tuned!
Hope this helps – RAM