Schema Validation in BizTalk 2010
Upcoming SlideShare
Loading in...5
×
 

Schema Validation in BizTalk 2010

on

  • 1,274 views

XMLschemas are not validated by default in BizTalk receive pipelines. However, you can configure OOTB components to do so. This slide deck shows two different ways you can achieve this, discussing the ...

XMLschemas are not validated by default in BizTalk receive pipelines. However, you can configure OOTB components to do so. This slide deck shows two different ways you can achieve this, discussing the pros & cons of each method.

Statistics

Views

Total Views
1,274
Views on SlideShare
1,274
Embed Views
0

Actions

Likes
2
Downloads
10
Comments
1

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

Schema Validation in BizTalk 2010 Schema Validation in BizTalk 2010 Presentation Transcript

  • www.briztalk.org SchemaValidation Validating Messages in a Receive Pipeline DanToomey MCPD, MCTS, MCT Brisbane BizTalk User Group Leader http://mindovermessaging.com/
  • www.briztalk.org XMLValidation in BizTalk • XmlReceive • BTS.MessageType == <targetNamespace>#<rootNodeName> XmlReceive XmlValidator
  • www.briztalk.org Using the XmlReceive Pipeline
  • www.briztalk.org Using the XmlReceive Pipeline • DocumentSpecNames
  • www.briztalk.org Using the XmlReceive Pipeline • DocumentSpecNames • ValidateDocument
  • www.briztalk.org Specifying Document Spec Names BrizTalk.SchemaValidation.Request1,BrizTalk.SchemaValidation, Version=1.0.0.0, Culture=neutral, PublicKeyToken=917e3a9ed61ea472
  • www.briztalk.org Specifying Document Spec Names | BrizTalk.SchemaValidation.Request1,BrizTalk.SchemaValidation, Version=1.0.0.0, Culture=neutral, PublicKeyToken=917e3a9ed61ea472 | BrizTalk.SchemaValidation.Request2, BrizTalk.SchemaValidation, Version=1.0.0.0, Culture=neutral, PublicKeyToken=917e3a9ed61ea472
  • www.briztalk.org Specifying Document Spec Names BizTalk Administration Console
  • www.briztalk.org Using the XmlReceive Pipeline PROS: • No custom components required • Can be configured by an administrator CONS: • Getting DocumentSpecNames correct can be tricky • Schema validation function is hidden • Problems if two or more schemas share the same target namespace
  • www.briztalk.org Using the XmlReceive Pipeline PROS: • No custom components required • Can be configured by an administrator CONS: • Getting DocumentSpecNames correct can be tricky • Schema validation function is hidden • Problems if two or more schemas share the same target namespace http://mindovermessaging.com/2013/07/29/ duplicate-namespace-issue-with-schema-validation-in-pipeline-components/
  • www.briztalk.org Using a Custom Pipeline XmlDisassembler Disassemble XmlValidator Validate
  • www.briztalk.org Using a Custom Pipeline PROS: • Don’t have to specify fully- qualified names of the schemas • Dedicated pipeline makes validation feature obvious • Better handling of multiple schemas sharing same target namespace CONS: • Requires component development & deployment
  • www.briztalk.org Summary XmlReceive XmlValidator
  • www.briztalk.org Brisbane BizTalk User Group https://www.facebook.com/BrisbaneBizTalkUserGroup @briztalk