Trading Networks 10.3 | Administering and Monitoring B2B Transactions | Service Development Help | Performing Data Validation | Performing Document Validation
 
Performing Document Validation
You might want to validate an individual document (IData object) in the pipeline instead of the entire pipeline. Use the pub.schema:validate service to validate a single document (IData object) in the pipeline against an IS document type.
For example, suppose that you invoke the pub.client.ldap:search service in a flow to retrieve an IData object from an LDAP directory service. If you want to validate that object before you use it in other services, invoke the pub.schema:validate service after retrieving the object. As another example, you might want to validate an XML document that has been converted to a document (IData object). You would use the pub.schema:validate service to validate the resulting document (IData object) against an IS document type.
The pub.schema:validate service considers a document (IData object) to be valid when it complies with the structural and content constraints described in the IS document type it is validated against. This service returns a string that indicates whether validation was successful and an IData array that contains any validation errors. When you insert the pub.schema:validate service into a flow service, you can specify the maximum number of errors that the service can collect. You can also specify whether the pub.schema:validate service should fail if the document (IData object) is invalid.
For more information about the pub.schema:validate service, see the webMethods Integration Server Built-In Services Reference
Note:
The validation engine in Integration Server can perform document (IData object) validation automatically when a document is published. For more information, see About Run-Time Validation for a Published Document.