Microsoft BizTalk Server 2006 R2 Standard, Chinese Traditional Disk Kit, MVL DVD 5 MLF D75-01321 User Manual
Product codes
D75-01321
24
respond to an event, that response will often take the form of a rule: If this event happens, then perform
that action. To make creating this kind of logic easier, developers can use the BizTalk Server BRE. The
BizTalk RFID server provides custom vocabularies to help developers create rules for working with
RFID.
that action. To make creating this kind of logic easier, developers can use the BizTalk Server BRE. The
BizTalk RFID server provides custom vocabularies to help developers create rules for working with
RFID.
In most cases, an RFID business process will need to communicate with other applications. (In fact,
this need for integration is the primary reason that
this need for integration is the primary reason that
Microsoft’s RFID support is licensed as part of
BizTalk Server.) An inventory application might need to be informed of stock changes, for example, or a
custom .NET application responsible for managing livestock might wish to keep track of each pig. As
Figure 14 shows, the RFID business process can communicate directly with other applications using
Web services, and it can also communicate with BizTalk Server 2006 R2. A BizTalk application might
use a WCF-based adapter to do this, since communication in the RFID server is based on WCF, or it
might use some other approach. In any case, the goal is to provide an effective way to turn low-level
events
custom .NET application responsible for managing livestock might wish to keep track of each pig. As
Figure 14 shows, the RFID business process can communicate directly with other applications using
Web services, and it can also communicate with BizTalk Server 2006 R2. A BizTalk application might
use a WCF-based adapter to do this, since communication in the RFID server is based on WCF, or it
might use some other approach. In any case, the goal is to provide an effective way to turn low-level
events
—reading RFID tags—into useful business knowledge.
Finally, as the figure shows, the BizTalk RFID server has its own RFID Manager. Using this tool, an
administrator can determine which RFID devices are running, examine and modify parameters on
those devices (such as which antennas are active on an RFID reader or what air protocol is used to
read RFID tags), and more. Microsoft also provides a management pack for Microsoft Operations
Manager 2005 and its successor System Center Operations Manager 2007, allowing the BizTalk RFID
server to be monitored and managed remotely.
administrator can determine which RFID devices are running, examine and modify parameters on
those devices (such as which antennas are active on an RFID reader or what air protocol is used to
read RFID tags), and more. Microsoft also provides a management pack for Microsoft Operations
Manager 2005 and its successor System Center Operations Manager 2007, allowing the BizTalk RFID
server to be monitored and managed remotely.
Enterprise Single Sign-On
A business process that relies on several different applications is likely to face the challenge of dealing
with several different security domains. Accessing an application on a Windows system may require
one set of security credentials, while accessing an application on an IBM mainframe may require
different credentials, such as a RACF username and password. Dealing with this profusion of
credentials is hard for users, and it can be even harder for automated processes. To address this
problem, BizTalk Server 2006 R2 includes Enterprise Single Sign-On.
with several different security domains. Accessing an application on a Windows system may require
one set of security credentials, while accessing an application on an IBM mainframe may require
different credentials, such as a RACF username and password. Dealing with this profusion of
credentials is hard for users, and it can be even harder for automated processes. To address this
problem, BizTalk Server 2006 R2 includes Enterprise Single Sign-On.
Don’t be confused—this isn’t a mechanism that lets people have one login for all applications. Instead,
Enterprise Single Sign-On provides a way to map a Windows user ID to non-Windows user credentials.
It won’t solve all of an organization’s enterprise sign-on problems, but this service can make things
easier for business processes that use applications on diverse systems.
Enterprise Single Sign-On provides a way to map a Windows user ID to non-Windows user credentials.
It won’t solve all of an organization’s enterprise sign-on problems, but this service can make things
easier for business processes that use applications on diverse systems.
To use Enterprise Single Sign-On, an administrator defines affiliate applications, each of which
represents a non-Windows system or application. An affiliate application might be a CICS application
running on an IBM mainframe, an SAP R/3 system running on Unix, or any other kind of software.
Each of these applications has its own mechanism for authentication, and so each requires its own
unique credentials.
represents a non-Windows system or application. An affiliate application might be a CICS application
running on an IBM mainframe, an SAP R/3 system running on Unix, or any other kind of software.
Each of these applications has its own mechanism for authentication, and so each requires its own
unique credentials.
Enterprise Single Sign-
On stores an encrypted mapping between a user’s Windows ID and his
credentials for one or more affiliate applications in a credential database. When this user needs to
access an affiliate application, his credentials for that application can be looked up in the Credential
database by a Single Sign-On (SSO) Server. Figure 15 shows how this works.
access an affiliate application, his credentials for that application can be looked up in the Credential
database by a Single Sign-On (SSO) Server. Figure 15 shows how this works.