Schema Validation in BizTalk 2010

  • 931 views
Uploaded on

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.

More in: Technology , Business
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
No Downloads

Views

Total Views
931
On Slideshare
0
From Embeds
0
Number of Embeds
0

Actions

Shares
Downloads
12
Comments
1
Likes
3

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide

Transcript

  • 1. www.briztalk.org SchemaValidation Validating Messages in a Receive Pipeline DanToomey MCPD, MCTS, MCT Brisbane BizTalk User Group Leader http://mindovermessaging.com/
  • 2. www.briztalk.org XMLValidation in BizTalk • XmlReceive • BTS.MessageType == <targetNamespace>#<rootNodeName> XmlReceive XmlValidator
  • 3. www.briztalk.org Using the XmlReceive Pipeline
  • 4. www.briztalk.org Using the XmlReceive Pipeline • DocumentSpecNames
  • 5. www.briztalk.org Using the XmlReceive Pipeline • DocumentSpecNames • ValidateDocument
  • 6. www.briztalk.org Specifying Document Spec Names BrizTalk.SchemaValidation.Request1,BrizTalk.SchemaValidation, Version=1.0.0.0, Culture=neutral, PublicKeyToken=917e3a9ed61ea472
  • 7. 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
  • 8. www.briztalk.org Specifying Document Spec Names BizTalk Administration Console
  • 9. 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
  • 10. 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/
  • 11. www.briztalk.org Using a Custom Pipeline XmlDisassembler Disassemble XmlValidator Validate
  • 12. 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
  • 13. www.briztalk.org Summary XmlReceive XmlValidator
  • 14. www.briztalk.org Brisbane BizTalk User Group https://www.facebook.com/BrisbaneBizTalkUserGroup @briztalk