webMethods Developer User's Guide - Software AG Documentation

10. Performing Data Validation
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 to be collected by the service. 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 performs document (IData object)
validation automatically when a document is published. The validation engine validates
the published document against the publishable document type.
Tip! If you want to validate only String, String list, or String table variables in the pipeline,
use the pub.schema:validatePipeline service. Define an IS document type that contains the
variables you want to validate and apply constraints to the variables. Then use this IS
document type as the blueprint for the pub.schema:validatePipeline service. Only the variables
in the IS document type will be validated. The validation engine ignores other variables
that exist in the pipeline at run time. (An IS document type implicitly allows unspecified
variables to exist at run time.)
Performing Pipeline Validation
Pipeline validation is the process of verifying the contents of the pipeline against an IS
document type. By validating pipeline data, you can:
� Ensure a higher degree of accuracy for pipeline content.
� Execute or not execute a service based on the validity of the pipeline data.
� Eliminate extra validation code in your service.
In pipeline validation, an IS document type is the blueprint or model against which you
validate the pipeline. The constraints applied to the variables in the IS document type
determine what can and cannot be included in the pipeline. For more information about
applying constraints to variables, see “Applying Constraints to Variables” on page 261.
To validate the pipeline, invoke the built-in service pub.schema:validatePipeline. This service
instructs the validation engine to compare the pipeline contents against a specified IS
document type. The pipeline is valid when it conforms to the structural and content
constraints applied to the IS document type. The pub.schema:validatePipeline service returns a
string that indicates whether validation was successful and an IData array (errors variable)
that contains any validation errors. For more information about the
pub.schema:validatePipeline service, see the webMethods Integration Server Built-In Services
Reference.
webMethods Developer User’s Guide Version 6.5, Service Pack 3 � � � 270