Integrating Integrators – BizTalk, Windows Azure, Windows Workflow, and Beyond

Re: Document Schema Vs Property Schema

BizTalk 2004

This group is for all content related to BizTalk Server 2004. This includes a forum, samples, videos, labs, whitepapers, and tools. Most of the content here also applies to other versions of BizTalk beyond 2004.

Document Schema Vs Property Schema

  • rated by 0 users
  • This post has 3 Replies |
  • Hi,

    What is the difference between a Document Schema and a Property Schema?

  • A document schema is used to define a message. It is a definition on an Xml message with optional extensions for flat files, EDI file, etc that enable the parsers to convert the native format into Xml.

    A property schema is used to define message context properties. These can be of type MessageDataPropertyBase (the property value is promoted or demoted from/to the message itself) or MessageContextPropertyBase(property value only exists within the message context and can be set by adapters, pipelines or within orchestrations).

    If you wish to promote a field from a message into the message context the you need to define a document schema and property schema. In the document schema you promote the required field using the property schema to define the property type that will be used in the message context.

    Message context properties are used for content based routing, correlation, modifying message content within orchestrations, etc.
  • Document schema is nothing but a normal schema  like ( which we create in general way).Whereas property schema means fields which we promote then those schema is called property schema


Page 1 of 1 (4 items)