Microsoft BizTalk Server 2006 R2 Standard, Chinese Traditional Disk Kit, MVL DVD 5 MLF D75-01321 Benutzerhandbuch
Produktcode
D75-01321
11
contain. To make defining XSD schemas easier, BizTalk Server 2006 R2 provides a tool called the
BizTalk Editor. Rather than creating a schema directly in XSD, this editor lets a developer build a
schema by defining its elements in a graphical hierarchy. Existing schemas can also be imported from
files or Web services.
BizTalk Editor. Rather than creating a schema directly in XSD, this editor lets a developer build a
schema by defining its elements in a graphical hierarchy. Existing schemas can also be imported from
files or Web services.
Once messages are in a known XML schema
, it’s possible to map between them. For example, it’s
common for some of the information in a received document to be transferred to a sent document,
perhaps transformed in some way. To allow this, BizTalk Server 2006 R2 lets developers create maps.
Each map is expressed as a correlation between two XML schemas that defines a relationship
between elements in those schemas. The W3C has defined the Extensible Stylesheet Language
Transformation (XSLT) as a standard way to express these kinds of transformations between XML
schemas, and so maps in BizTalk Server 2006 R2 are implemented as XSLT transformations.
perhaps transformed in some way. To allow this, BizTalk Server 2006 R2 lets developers create maps.
Each map is expressed as a correlation between two XML schemas that defines a relationship
between elements in those schemas. The W3C has defined the Extensible Stylesheet Language
Transformation (XSLT) as a standard way to express these kinds of transformations between XML
schemas, and so maps in BizTalk Server 2006 R2 are implemented as XSLT transformations.
Maps can be used in various ways. Suppose, for instance, that an incoming purchase order needs to
have some of its information mapped to an outgoing invoice. A developer might create a map that does
this, then invoke that map from a send pipeline
have some of its information mapped to an outgoing invoice. A developer might create a map that does
this, then invoke that map from a send pipeline
—no orchestration is required. In a more complex case
that requires more business logic, a map might be invoked from within an orchestration. For example,
an order fulfillment process might receive an order for some number of items, then send back a
message indicating that the order was declined for some reason. It’s possible that information from the
order, such as a request identifier and the quantity ordered, should be copied from fields in the received
order message into fields in the rejection message.
an order fulfillment process might receive an order for some number of items, then send back a
message indicating that the order was declined for some reason. It’s possible that information from the
order, such as a request identifier and the quantity ordered, should be copied from fields in the received
order message into fields in the rejection message.
Maps are just XSLT, so an ambitious developer is free to build them by hand. To make this task easier,
BizTalk Server 2006 R2 provides a graphical tool called the BizTalk Mapper. Figure 8 shows how a
map for transferring information from a contacts database into a CRM application might look.
BizTalk Server 2006 R2 provides a graphical tool called the BizTalk Mapper. Figure 8 shows how a
map for transferring information from a contacts database into a CRM application might look.
Figure 6: The BizTalk Mapper allows specifying how information in one message should be mapped
to another message.
The transformation defined in a map can be simple, such as copying values unchanged from one
document to another. Direct data copies like this are expressed using a link, which is shown in the
BizTalk Mapper as a line connecting the appropriate elements in the source schema with their
document to another. Direct data copies like this are expressed using a link, which is shown in the
BizTalk Mapper as a line connecting the appropriate elements in the source schema with their