Microsoft BizTalk Server 2006 R2 Standard, IT Disk Kit, MVL DVD 5 MLF D75-01324 Manuale Utente
Codici prodotto
D75-01324
17
contains only a single instance of
the MessageBox database, it’s possible to replicate this database for
greater scalability or cluster it to avoid creating a single point of failure.
Managing BizTalk Applications
Whatever it does
and however it’s configured, every BizTalk application must be managed. What’s the
state of running applications right now? How have applications behaved in the past, and how can this
knowledge be used to improve the future? This section looks at the tools provided to answer these
questions.
knowledge be used to improve the future? This section looks at the tools provided to answer these
questions.
Creating and Monitoring Applications
The primary tool for creating, monitoring, and managing BizTalk applications is the BizTalk
Administration console, a Microsoft Management Console (MMC) snap-in that provides a standard
user interface for BizTalk administrators. While this tool gives administrators a number of capabilities,
the most important are the ability to do three things:
The primary tool for creating, monitoring, and managing BizTalk applications is the BizTalk
Administration console, a Microsoft Management Console (MMC) snap-in that provides a standard
user interface for BizTalk administrators. While this tool gives administrators a number of capabilities,
the most important are the ability to do three things:
Deploy BizTalk applications. Using the BizTalk Administration console, an admin can create a
BizTalk application, deploy it to one or more servers, and more.
BizTalk application, deploy it to one or more servers, and more.
Configure BizTalk applications. When a developer creates an orchestration, she works largely in
logical terms. To define how BizTalk Server 2006 R2 will communicate with a particular application,
for example, the developer can select the WCF SOAP adapter without worrying about the specific
URL that will be used. Similarly, she can specify that the send pipeline should include a component
that adds a digital signature to outgoing messages without worrying about exactly what key will be
used to create this signature. Yet to make the application work, these details must be specified.
The BizTalk Administration console allows an admin to create and modify details like these.
logical terms. To define how BizTalk Server 2006 R2 will communicate with a particular application,
for example, the developer can select the WCF SOAP adapter without worrying about the specific
URL that will be used. Similarly, she can specify that the send pipeline should include a component
that adds a digital signature to outgoing messages without worrying about exactly what key will be
used to create this signature. Yet to make the application work, these details must be specified.
The BizTalk Administration console allows an admin to create and modify details like these.
Monitor and manage BizTalk applicati
ons. Using the BizTalk Administration console’s Group Hub
page, an administrator can monitor the operation of BizTalk applications. As Figure 11 shows,
information about the status of these applications can be examined in various ways. An
administrator can look at currently running applications, for example, suspending and restarting
them as necessary.
information about the status of these applications can be examined in various ways. An
administrator can look at currently running applications, for example, suspending and restarting
them as necessary.
It’s also possible to look more closely at individual applications, examining
specific messages or other details. And rather than requiring an administrator to search for
problems, the Group Hub page uses color-coded indicators to display those problems. This lets
administrators take a more proactive approach to application monitoring.
problems, the Group Hub page uses color-coded indicators to display those problems. This lets
administrators take a more proactive approach to application monitoring.