Pipeline validation is the process of verifying the contents of the pipeline against an IS document type. By validating pipeline data, you can:

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 About Variable Constraints.

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.

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. Integration Server validates only the variables in the IS document type. 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.)