The Xml parameter is converted in a string parameter in the generated code. So for passing an XML, you need to convert it in string with encoding.

It exists a simpler manner :

• In your orchestration, only create your XML parameter as a message
• Send it via your send port to WCF-SQL
• Now in the send port click on configure
• Click the Messages tab, and in the Outbound WCF message body section, choose the Template option.
• In the XML text box, specify the template that will be used to construct the WCF message. By doing so, you create a message that conforms to the operation for the WCF-based SQL adapter
• 
• For the ADD_LAST_EMP_XML_INFO stored procedure, you must specify the following template:

  <ADD_LAST_EMP_XML_INFO xmlns="http://schemas.microsoft.com/Sql/2008/05/Procedures/dbo">
  <xml_info>
  <bts-msg-body xmlns="http://www.microsoft.com/schemas/bts2007" encoding="string"/> </xml_info>
  </ADD_LAST_EMP_XML_INFO>

• The Tag encoding is very important. By specifying string, it’ll replace <> and other special caracter by their encoding (like &gt; …)

Some concerns SQL, and other windows environement, but all are required; in my experience, I always followed this requirements.

MSDN

MDSN is a huge online repository for Microsoft documentation. This should be your primary source for information on BizTalk availability:

• Planning Your Platform for Fault Tolerance 
• Creating a Highly Available BizTalk Server Environment
• Sample BizTalk Server High Availability Scenarios
• High Availability for Enterprise Single Sign-On
• High Availability and the Microsoft Operations Framework
• Getting Started with SQL Server 2008 Failover Clustering
• Improving Fault Tolerance in BizTalk Server by Using a Windows Server Cluster

Articles

The following articles provide more information on High Availability for BizTalk:

• Recommendations for Installing, Sizing, Deploying, and Maintaining a BizTalk Server Solution
• White Paper: SQL Server 2008 Failover Clustering

Blogs

The following blog posts by community provide more background information and experience on High Availability for BizTalk:

• Clustering BizTalk Hosts
• BizTalk High Availability Host Separation
• Installation of SSO on SQL Cluster
• BizTalk High Availability Server Environment –BizTalk 2010 Installation, Configuration and Clustering
• How To Cluster BizTalk’s MSMQ Receive Adapter – Windows 2008 Server
• BizTalk High Availability Server Environment – Preparations

Webcasts

The following web casts by community provide more background information on High Availability for BizTalk:

• Creating a Highly Available BTS Environment
• MSDN Webcast: High Availability, Fault Tolerance and Scalability with BizTalk Server 2006

See Also

• Improving Fault Tolerance in BizTalk Server by Using a Windows Server 2008 Failover Cluster or Windows Server 2003 Server Cluster  
• Microsoft BizTalk Server 2010 Performance Optimization Guide

source : http://social.technet.microsoft.com/wiki/contents/articles/6532.aspx

You’ve got two ways for this :

The first one by editing the config file,

Add this section :

 <microsoft.applicationServer> 
    <monitoring> 

      <default enabled="true" connectionStringName="DefaultApplicationServerExtensions" monitoringLevel="Troubleshooting" /> 
    </monitoring> 
</microsoft.applicationServer>

The connectionStringName attribute should contain a reference to an existing connection string in the ConnectionString section, and that’s the database used by AppFabric to store the monitoring events.

The monitoringLevel attribute specifies the number of events you want to capture in a service execution. The possible values for this setting are,

• Off (monitoringLevel=”Off”): No data is collected. It would be equivalent to have monitoring disabled.
• Errors only (monitoringLevel=”ErrorsOnly”):  Only errors and warnings events are collected. This is very useful when you don’t want to incur into performance issues for collecting application events but you still want to know about any error may happen during the execution.
• Health Monitoring (monitoringLevel=HealthMonitoring): This is the default level and collects enough application events to show different metrics in the AppFabric dashboard.
• End To End Monitoring (monitoringLevel=”EndToEndMonitoring”). It collects all the events from the Health Monitoring level, plus additional events to reconstruct the message flow. For example, Service A called Service B. You will get also events representing info about the Service B call if monitoring is enabled on Service A.
• Troubleshooting (monitoringLevel=”Troubleshooting”). This is the most verbose of all, so it is appropriate for troubleshooting an unhealthy application.

The second way is more friendly use :

On the web you can find lot of solution like updating regiter key or delete web debug server.

But the simpliest technic is to disable the project to start the debug asp server :

Click on the project, then go to the property tab and set to false the property “Always Start When debugging” :

Now let’s wait for a beta version to test it, say good luck to the BizTalk DEV team.

Here is the original article on MSDN : http://blogs.msdn.com/b/biztalk_server_team_blog/archive/2011/12/08/biztalk-server-2010-r2.aspx

This tool is very powerfull but never really used, and often misunderstood.

For helping, Technet did a great job with these series of article about BAM. You can get general informations or very technical ones.

I’ve got just one remark, there is no explanation for when implementing BAM or about the potential, my coleague Hugues Moore wrote an article about the BAM capabilities. In a futur article, I’ll write about how to use it in real condition.

For the moment here is the link I talked about

http://social.technet.microsoft.com/wiki/contents/articles/5599.aspx

“projects have recently been added to this solution do you want to get them from source control”. I think this “problem” come from some migration because, I always get this error with some project which I migrated.

This problem is not important but if you want to clear it here is the step for :

1. Unbind the solution from TFS (Do this by going to File/Source Control/Change Source Control menu item)

2. Edit the .sln file manually and remove all sections that look like ”GlobalSection(TeamFoundationVersionControl) = preSolution”. Those sections could be very large, but don’t worry, Visual Studio will regenerates those.

3. Rebind the solution with TFS

With this tips you can also clear the issue : “Some of the properties associated with the solution could not be read“

here is some articles  found for BizTalk Server 2010 :

• Working with BizTalk AppFabric Connect
  • Installing the BizTalk Server 2010 AppFabric Connect feature
  • BizTalk + WF/WCF, Better Together
  • BizTalk Server 2010 AppFabric Connect feature Frequently Asked Questions (FAQ)
• Exposing LOB Services on the Cloud Using AppFabric Connect for Services
• Exposing BizTalk Applications on the Cloud using AppFabric Connect for Services
• Load Testing BizTalk Server Solutions with Visual Studio 2010
• Create a Load Test to Perform Multiple Unit Tests Simultaneously
• Install and Configure BAM (Business Activity Monitoring) in a Multi-Computer Environment
• Invoking ReSTful Web Services with BizTalk Server 2010
• How to use NServiceBus to do Broadcast Message Distribution with BizTalk Server RFID
• Querying and Creating Records in Dynamics CRM 2011 from BizTalk Server 2010
• BizTalk Server integration with SharePoint Server using WSS Adapter
• Typed Polling with WCF-SQL Adapter: Best Practices and Troubleshooting Tips 
• BizTalk Server 2010 Exam 70-595 Preparation
• BizTalk Databases: Survival Guide
• BizTalk Server 2010 Beginners Guide
• BizTalk Server 2010
• BizTalk Server Adapter Pack 2010
• BizTalk Server Documentation

Hopefully you find one of more article that are useful for you to learn about capabilities of BizTalk or new ways to integrate with BizTalk.

(source : http://soa-thoughts.blogspot.com/2011/10/biztalk-server-technet-wiki-articles.html)

The BizTalk Adapter Pack 2010 provides connectivity to SAP, Oracle E-Business Suite, Siebel and SQL and Oracle Databases. The BizTalk Adapter Pack can be installed in conjunction with, or separately from, BizTalk Server.

The BizTalk Adapter Pack 2010 includes support for new versions of the following line-of-business applications and databases: SAP 7, Oracle EBS 12.1 and SQL Server 2008 R2. The Adapter Pack also provides support for Visual Studio 2010 and .NET Framework 4.

It is included in both the Enterprise and Standard Editions of BizTalk. When you install the adapter pack on x64 environment you have to perform a few steps. These steps were described in earlier versions through installation guides, although for some it was not always clear (i.e. I saw couple of questions on forum about how to install or problems people had). There is documentation to install adapters pack, but now during installation one is guided through the necessary steps.

First re-execute the BizTalk  instalation wizzard and select install adapter Pack.

You’ll get this screen :

For a developper, you need to install each item in the complete version.

At the end go to BizTalk administration console -> plateform setting -> adapter.

Right click on it and select “add new adapter” and normaly you’ll obtain this screen :

Name it and press OK, now you can play with newly created adapter (don’t forget to restart host)

Those are very usefull to present an architecture, or when I provide training, they permit to all trainee to locate which brick we’ve manipulate

Poster theme :

• BizTalk Server 2010 ESB Toolkit Architecture Poster
• BizTalk Server 2010 Capabilities Poster
• BizTalk Server 2010 Run-Time Architecture Poster
• BizTalk Server 2010 Scale-out Configurations Poster
• BizTalk Server 2010 Database Infrastructure Poster
• BizTalk Server 2010 BAM Poster
• BizTalk Adapter Pack 2010 Poster

http://msdn.microsoft.com/en-us/biztalk/dd807494.aspx

All poster are available for BizTalk 2009 too