A schema specifies the structure of an XML document and constraints on its content.
Define the structure of all messages that it processes, and refers to these definitions of message structure as schemas. With few exceptions, structured messages are the core of any application. These structured messages can take any form, large or small, and target a wide array of back-end systems and data stores. Systems that create and consume the structured messages frequently use different formats. Two of the most common formats for structured messages are XML and flat files.
BizTalk Editor is designed to simplify the process of defining a message schema and validating whether a particular message conforms to that schema. In the process of defining schemas and validating messages, you will likely perform some of the following tasks:
• Create schemas for structured XML messages.
• Create schemas for flat file messages.
• Generate schemas from well-formed XML instance data.
• Validate message conformance to a specific schema.
• Perform design-time validation of schemas.
Different Types of BizTalk Schemas
XML schema: An XML schema defines the structure of a class of XML instance messages. Because this type of schema uses XML Schema definition (XSD) language to define the structure of an XML instance message, and this is the intended purpose of XSD, such schemas use XSD in a straightforward way.
Flat file schema: A flat file schema defines the structure of a class of instance messages that use a flat file format, either delimited or positional or some combination thereof. Because the native semantic capabilities of XSD do not accommodate all of the requirements for defining the structure of flat file instance messages—such as the various types of delimiters that might be used for different records and fields within the flat file—BizTalk Server uses the annotation capabilities of XSD to store this extra information within an XSD schema. BizTalk Server defines a rich set of specific annotation tags that can be used to store all of the required additional information.
Envelope schema: An envelope schema is a special type of XML schema. Envelope schemas are used to define the structure of XML envelopes, which are used to wrap one or more XML business documents into a single XML instance message. When you define an XML schema to be an envelope schema, a couple of additional property settings are required, depending on such factors as whether there are more than one root record defined in the envelope schema.
Property schema: A property schema is used with one of the two mechanisms that exist within BizTalk Server for what is known as property promotion. Property promotion is the process of copying specific values from deep within an instance message to the message context. From the message context, these values are more easily accessed by various BizTalk Server components. These components use the values to perform actions such as message routing. Promoted property values can also be copied in the other direction, from the more easily accessible message context back into the depths of the instance message, just before the instance message is sent to its destination. A property schema is a simple version of a BizTalk schema that plays a role in the process of copying promoted properties back and forth between the instance message and the message context.
Comments
Post a Comment
Please write comment only that belongs to this blog