BizTalk Application on the cloud using AppFabric Connect for Services

BizTalk Server 2010 introduces a new feature “AppFabric Connect”, which combines rich proven features of BizTalk Server with the flexible development experience of .NET to allow users to easily develop simple integration applications. This enables users to:

Develop custom .NET applications that require connectivity to backend Line of Business (LOB) systems like SAP, Oracle database, Oracle E-Business Suite, Seibel, and SQL Server without writing custom code for LOB connectivity
Utilize the XML-based data transformation capabilities of the easy to use and rich interface of the BizTalk Server Mapper directly from within a .NET project.

BizTalk Server 2010 RTM and General Availability Date Announced

BizTalk Server 2010 RTM and General Availability Date Announced

http://blogs.msdn.com/b/nikosan/archive/2010/09/28/biztalk-server-2010-training-now-available.aspx

BizTalk Server 2009 Live Demo

A live demo of BizTalk 2009 with hands on labs are available now, you can download offline VPC image for BizTalk 2009 from the below link.

http://blogical.se/blogs/johan/archive/2009/10/18/biztalk-server-2009-vpc.aspx

Enjoy
Cheers :)

Model View Controler (MVC) Song

Service Oriented Architecture Overview (e-Framework)

dotNETwork 7th Gathering: Tec-Talk wiz BizTalk

Increasing Availability for BizTalk Server

How you can increase the availability of your BizTalk Server system?

I have been asked this question before, first think that comes to my mind is that you can easily redundant the servers which hosts your BizTalk application this was good answer at this time but after that i decide to know more about this i read too many articles concerning this issue plus disaster recovery and it ends up to the following .

there are many strategies you can follow to reach high availability but first lets explain the difference between high availability and disaster recovery.

Disaster recovery allows you to resume operation of a failed system but is typically a manual process and requires more recovery time than a high-availability implementation. Therefore, a disaster recovery implementation provides availability but not high availability. You should employ both high availability through server clusters and load balancing, and availability through disaster recovery, in a production BizTalk Server environment.

Now what are the strategies for high availability of your BizTalk application:

• Providing high availability using Windows Clustering. A server cluster is a group of independent computer systems, known as nodes, working together as a single system to ensure that critical applications and resources remain available to clients. If one of the nodes becomes unavailable as a result of failure or maintenance, another node immediately begins providing service (a process known as failover).
• A server cluster is typically recommended for the computers running SQL Server that house the BizTalk Server databases.
• A server cluster may be required to provide high availability for certain BizTalk adapters.
• A server cluster is typically recommended for the Enterprise Single SignOn master secret server.
• Providing high availability using Network Load Balancing (NLB). NLB delivers high availability by redirecting incoming network traffic to working cluster hosts if a host fails or is offline. Unlike server clusters, NLB does not require special hardware.NLB is provided for BizTalk Hosts by adding multiple servers to a group.Load balancing is provided for SQL Server disks through the use of a SAN or by adding multiple MessageBox databases.
• Increasing availability using BizTalk Server log shipping and disaster recovery.
• Increasing availability through implementation of the appropriate monitoring and maintenance strategies.