BizTalk Server 2010 操作指南：规划与管理实践

需积分: 7 66 浏览量更新于2024-07-23 收藏 3.19MB PDF 举报

"BizTalkServer2010-OperationsGuide" 《BizTalk Server 2010 操作指南》是针对参与BizTalk解决方案实施与管理的IT专业人员的重要参考资料。该指南详细阐述了规划BizTalk Server环境的步骤，以及配置、测试、维护和监控环境的最佳实践。它旨在帮助BizTalk用户顺利完成所有关键任务，提供了全面的检查列表。 BizTalk Server 2010是微软公司推出的企业级集成平台，用于连接不同的业务系统，实现数据交换和流程自动化。操作指南在2011年2月发布，其内容覆盖了以下几个主要方面： 1. **环境规划**：指南详细介绍了如何根据组织的需求来规划BizTalk Server的架构，包括硬件和软件需求、网络设计、数据库配置以及高可用性方案。 2. **安装与配置**：提供了一步一步的安装指导，涵盖了 BizTalk Server 的各个组件，如BizTalk Server本身、数据库服务器、管理工具和其他必要的服务。 3. **最佳实践**：分享了在部署和运行BizTalk Server时应遵循的实践，以确保系统的稳定性和性能。这包括服务器配置优化、安全策略和日志管理等。 4. **测试与验证**：包含了测试 BizTalk 解决方案的方法，确保在生产环境中能够正常运行。此外，还讨论了性能基准测试和压力测试。 5. **维护与监控**：详细阐述了监控 BizTalk 环境的关键指标，以及如何定期进行健康检查和性能调优。此外，还介绍了故障排查和备份恢复的策略。 6. **安全与合规**：指南强调了数据安全和法规遵从的重要性，提供了设置安全策略、权限管理和审计跟踪的建议。 7. **故障排除**：提供了针对常见问题的解决方案，帮助IT专业人员快速定位并解决运行时遇到的问题。 8. **检查列表**：每个关键任务都配有检查列表，帮助管理员确保没有遗漏任何重要步骤，确保流程的顺利进行。《BizTalk Server 2010 操作指南》是BizTalk管理员的必备工具，它提供了全面的指导，帮助用户有效地管理和维护BizTalk Server环境，确保系统的高效稳定运行。通过遵循指南中的最佳实践，IT专业人员可以更好地利用BizTalk Server实现企业级的集成和流程自动化。

that are fixed in Windows Server 2003 MS DTC Hotfix Rollup Package 16"

(http://support.microsoft.com/kb/979919).

The KB article about the latest DTC hotfix rollup package can be found by searching

http://support.microsoft.com for the phrase (including the quotes):

"MS DTC Hotfix Rollup Package"

The following query does this search for you. Choose the latest one:

http://support.microsoft.com/search/default.aspx?query="MS+DTC+Hotfix+Rollup+Package"

Disabling Windows Server 2003 SP1 and SP2 Denial of Service Checking

This topic is applicable only for Windows Server 2003.

You should disable the Windows Server 2003 Service Pack 1 and Service Pack 2 denial of

service checking. This is because under certain high-load scenarios, Windows Server 2003 SP1

and SP2 denial of service checking may incorrectly identify valid TCP/IP connections as a denial

of service attack.

You should disable this feature only in an intranet scenario when you are sure you will

not suffer from actual denial of service attacks.

How Denial of Service Can Affect TCP/IP Connections

Windows Server 2003 SP1 and SP2 implement a security feature that reduces the size of the

queue for concurrent TCP/IP connections to the server. This feature helps prevent denial of

service attacks. Under heavy load conditions, the TCP/IP protocol in Windows Server 2003 SP1

or later may incorrectly identify valid TCP/IP connections as a denial of service attack. This may

occur when BizTalk Server is under heavy load.

Modifying the Registry Entry

For more information, see Microsoft Knowledge Base article 899599, "A BizTalk Server Host

instance fails, and a 'General Network' error is written to the Application log when the BizTalk

Server-based server processes a high volume of documents"

(http://go.microsoft.com/fwlink/?LinkId=158860). Follow the instructions in this article to create the

SynAttackProtect registry entry on computers running SQL Server that host BizTalk Server

databases and on any computers running BizTalk Server that are running Windows Server 2003

SP1 or later.

Tuning Registry Settings that Govern the Level of Denial of Service Attack Protection

In certain scenarios you may want to maintain denial of service protection but reduce how

aggressively the denial of service functionality is applied. It is possible to tune the default

behavior of the denial of service protection feature by following these steps:

1. Ensure that the SynAttackProtect registry entry is set to a REG_DWORD value of 1 as

described at http://go.microsoft.com/fwlink/?LinkId=111477.

2. Configure the TcpMaxHalfOpen registry entry as described at

http://go.microsoft.com/fwlink/?LinkId=111478.

Note

Important

3. Configure the TcpMaxHalfOpenRetried registry entry as described at

http://go.microsoft.com/fwlink/?LinkId=111479.

See Also

Checklist: Configuring Windows Server

Checklist: Configuring Internet Information Services

This topic lists steps that should be followed when preparing Internet Information Services (IIS)

for use in a production BizTalk Server environment.

Steps

Reference

Set up IIS to publish BizTalk Server

Web services and WCF services

 See "Enabling Web Services"

(http://go.microsoft.com/fwlink/?LinkId=153335) in

the BizTalk Server documentation.

 See "Configuring IIS for the Isolated WCF Receive

Adapters"(http://go.microsoft.com/fwlink/?LinkId=202

825) in the BizTalk Server documentation.

Verify that BizTalk Server Web

services and WCF services are

working correctly.

 See "Testing Published Web Services"

(http://go.microsoft.com/fwlink/?LinkId=153336) in

the BizTalk Server documentation.

 See "How to Create a .NET Application to Test a

Steps

Reference

WCF Service Published with the BizTalk WCF

Service Publishing Wizard"

(http://go.microsoft.com/fwlink/?LinkId=202830) in

the BizTalk Server documentation.

Lock down BizTalk Server Web

services:

 Turn off the Debug switch in the

web.config or machine.config file.

 Configure so that POST is the

only verb allowed.

 See Microsoft Knowledge Base Article 815145,

"HOW TO: Lock Down an ASP.NET Web Application

or Web Service"

(http://go.microsoft.com/fwlink/?LinkId=153337).

 See "ASP.NET Edit Rule Dialog Box"

(http://go.microsoft.com/fwlink/?LinkID=64566) in the

.NET Framework 2.0 documentation.

Configure load balancing by using

NLB (or other load balancer) to

balance load across BizTalk Server

Web services and WCF services.

 For Windows Server 2008: See "Network Load

Balancing Deployment Guide"

(http://go.microsoft.com/fwlink/?LinkId=153139).

 For Windows Server 2003: See "Network Load

Balancing: Configuration Best Practices for Windows

2000 and Windows Server 2003"

(http://go.microsoft.com/fwlink/?LinkID=69529).

Change IIS and ASP.NET settings for

tuning Web services.

Note

ASP.NET 2.0 includes auto-

tuning, so modifying these

settings should not be needed

for the web.config file of

ASP.NET 2.0 Web sites

where autoConfig is enabled

in the <processModel>

section. ―autoConfig=true‖ is

the default setting.

Review the "ASP.NET settings that can impact HTTP or

SOAP Adapter performance‖ section of the topic

"Configuration Parameters that Affect Adapter

Performance"

(http://go.microsoft.com/fwlink/?LinkId=153338) in the

BizTalk Server documentation.

Implement an approach for publishing

BizTalk Server Web services and

WCF services.

 See Publishing Internet-facing Web Services and

WCF Services.

 See "Publishing WCF Services"

(http://go.microsoft.com/fwlink/?LinkId=202827) in

the BizTalk Server documentation.

Follow best practices for optimizing

IIS performance.

See "Top Ten Ways To Pump Up IIS Performance"

(http://go.microsoft.com/fwlink/?LinkId=109107).

Follow best practices for writing high

performance web applications for IIS.

See "10 Tips for Writing High-Performance Web

Applications"

Steps

Reference

(http://go.microsoft.com/fwlink/?LinkId=98290).

In This Section

 Publishing Internet-facing Web Services and WCF Services

Publishing Internet-facing Web Services and WCF Services

You can use multiple approaches for publishing BizTalk Server Web services and WCF services

to the Internet:

 Use reverse proxy rules in a perimeter network (also known as DMZ, demilitarized zone, and

screened subnet).

 Put the computers running BizTalk Server that publish the Web services or WCF services

into the perimeter network domain.

 Use BizTalk Server 2010 cloud enabler functionality to publish the Web services or WCF

services as an Azure AppFabric Service Bus relay endpoint.

Using a Reverse Proxy

This has been the traditional approach for publishing BizTalk Server Web services and WCF

services. Using reverse proxy rules in the perimeter network obviates the need to have BizTalk

servers located in the perimeter network. The reverse proxy rules simply forward the HTTP and

SOAP requests from the perimeter network to the computers running BizTalk Server in the

intranet domain.

For more information about using a reverse proxy, see the following topics in BizTalk Server 2010

Help:

 "Sample Architecture: HTTP and SOAP Adapters"

(http://go.microsoft.com/fwlink/?LinkId=153339).

 "Sample TMA: HTTP and SOAP Adapters" (http://go.microsoft.com/fwlink/?LinkId=153340).

 "Large Distributed Architecture" (http://go.microsoft.com/fwlink/?LinkId=153341).

Using Computers Running BizTalk Server in the Perimeter Network

This is not the preferred approach for publishing BizTalk Server Web services or WCF services to

the Internet because it requires computers running BizTalk Server to be located in the perimeter

network. However, when a reverse proxy is not available in the perimeter network, you can use

this approach.

This approach requires the perimeter network domain to enlist in a one-way trust with the intranet

domain (but the intranet domain does not trust the perimeter network domain). The IIS application

pools that host the Web services or WCF services in the perimeter network domain must be

running under an intranet domain account that is in the "BizTalk Isolated Host Users" domain

group. This gives the application pool the required rights to publish messages to the BizTalk

Server MessageBox database.

You must open specific ports in the firewall to accommodate this. For more information about the

required ports, see "Ports for the Receive and Send Servers"

(http://go.microsoft.com/fwlink/?LinkId=153342) in the BizTalk Server documentation.

Exposing BizTalk Applications on the Cloud using AppFabric Connect for Services

See the article Exposing BizTalk Applications on the Cloud using AppFabric Connect for Services

(http://go.microsoft.com/fwlink/?LinkID=204700) for more information about expose BizTalk

Applications as WCF Services on the cloud.

BizTalk Server 2010 操作指南：规划与管理实践

微软BizTalkServer：数据交换与企业级解决方案

微软案例：SOA技术实现应用程序高效集成

BizTalk Server 2010安装指南

BizTalk Server 2010

BizTalk2010教程中文版

biztalkserver 安装包

SOA实践：微软如何整合不同应用系统

基于 C++构建 Qt 实现的 GDAL 与 PROJ4 的遥感图像处理软件课程设计

【java毕业设计】娜娜服装企业物流管理系统源码（完整前后端+说明文档+LW）.zip

2009年国际大学生数学建模竞赛成果公告

最新资源