Microsoft published SP1 for BizTalk Server 2006 R2. You can find it here.
From the Microsoft site:
Better reliability, performance, and scale for the following key features:
- Throttling and dehydration of orchestrations.
- Archiving and purging operations.
- BAM alerts and archiving.
- HIPAA.
- Reduced memory consumption in scenarios using scripting functoids.
- Improvement in the bts_FindSubscription stored proc, resulting in faster execution and lower CPU utilization.
Better management and deployment experiences:
- Performance and user experience improvements of key scenarios.
- WCF configuration management.
- Significant improvement in deployment time for send ports using a map.
Improved support:
- X12 and EDIFACT updates.
- Increased footprint of supported FTP servers and locale.
- XMLDocument message types in orchestrations.
- Configurable timeout for Basic HTTP.
- WCF adaptor now suspends messages instead of terminating when the host instance is stopped.
- Configurable transaction timeout for WCF Adaptors.
- Mapping of inline schema for SQL Adaptor now allows for using $ characters as part of the updategram.
- The SQL Adaptor now supports calling from a BizTalk Server dynamic send port. The following properties can be set on the call to the dynamic port:
Connection string (all the SQL connection properties)
Document Target Namespace
Response Document Root Element- Ability to disable generation of Routing Failure Report.
- Fixes to some issues that used to cause high CPU usage by BizTalk Server hosts due to certain .NET updates.
- Ability to use multiple certificates for signing outbound messages.
- Message Pack 2009.
- Message property tracking with BAM for all messages in the interchange, irrespective of the usage of pipeline or mapping.
- Integrated tracing to help in debugging EDI specific issues. This improvement is aimed at reducing the time taken for diagnosing and isolating an EDI problem.
New Features:
- For WCF-Custom and WCF-CustomIsolated Adapters, the ability to look up custom bindings from locations other than machine.config.
- Support for using multiple certificates to sign outgoing AS2 messages.
). Note: I wouldn’t have a problem when our integration test server machine was part of the daily build (so automated integration tests). Nice discussion. Leave some comments on how you feel about this.
