Ganesh Narayanan's BizTalk Hints

What’s in a BizTalk Host:

1. Thread Management
2. Memory Management
3. Service Isolation
4. Exception Configuration
5. Failed Message Management
6. Message Tracking
7. Composite Execution Tracking
8. Composite State Management
9. Load Balancing
10. Fail-over
11. Throttling
12. Scale-out Configuration
13. Scripting and Programmability APIs
14. Regulatory Compliance
15. Archiving and Purging
16. Disaster Recovery
17. Utilization/Performance Tracking
18. Health Monitoring
19. Availability Monitoring
20. Multi-environment Deployment Model
21. Configuration Management
22. Identity and Impersonation

Extracted from a Microsoft Canada Presentation prepared by Peter Kelcey

This has been blogged by others previously. I am adding this here for my reference:

/*[local-name()='Fault']/*[local-name()='Detail' or local-name()='detail']/* |/*[not(local-name()='Fault')]

Here is the expression for WCF.InboundBodyPathExpression to be used in the Expression Editor for ExecuteReaderResponse for a Dynamic WCF SQL Adapter:

msgQuery(WCF.InboundBodyLocation)="UseBodyPath";

msgQuery(WCF.InboundBodyPathExpression)="/*[local-name()='ExecuteReaderResponse']/*[local-name()='ExecuteReaderResult']/*[local-name()='DataSet']/*[local-name()='diffgram']/NewDataSet";

msgQuery(WCF.InboundNodeEncoding)="XML";

This has been blogged several times already. I am making this entry here for my reference.

Steps to enable basic ESB 2.0 Exception handling in an orchestration:

1. Create Multipart message type “Fault” with “Body” of type Microsoft.Practices.ESB.ExceptionHandling.Schemas.Faults.FaultMessage
2. Create new message msgFault with above type
3. Create Exception Handler sysEx of type System.SystemException
4. Construct message with following expressions:

Until the days of Biztalk 2006R2, the SQL Port was Static only and did not support dynamic ports.

BizTalk 2009 fully supports Dynamic SQL Ports, both for the regular out-of-the-box SQL Adapter and the new WCF SQL adapter.

For the regular SQL Adapter (which is being deprecated by microsoft), three new Message Context properties are available:

(SQL.ResponseDocumentRootElementName)

(SQL.DocumentTargetNamespace)

(SQL.ConnectionString)

Configuring these properties, together with

(Microsoft.XLANGs.BaseTypes.Address)="SQL://" +Servername/ + Databasename/

creates a fully functional Dynamic SQL Adapter.

For the WCF SQL adapter, follow the steps in the link:

http://msdn.microsoft.com/en-us/library/dd788439(BTS.10).aspx

When consuming a WCF Service in BizTalk, I came across the error: The action is invalid or unrecognized.

The reason was that when I created the logical Request/Response port for the service in the orchestration, I used a new port type.

When generating the files for consuming the service, BizTalk had automatically created a Port Type for the Request/Response port. When I used this port type, the error went away.