Blueprints or Models Against which Data is Validated
During validation, run-time data is compared to a blueprint or model. The blueprint or model is a formal description of the structure and the allowable content for the data. The blueprint identifies structural and content constraints for the data being validated. The validation engine in Integration Server considers the data to be valid when it conforms to the constraints specified in the blueprint. A blueprint can be an IS schema, an IS document type, or a set of input and output parameters.
The blueprint used to validate data depends on the type of validation you are performing. In Integration Server, you can perform the following types of validation:
Input/Output validation. The validation engine in
Integration Server validates the input and/or output of a service against the signature of the service.
Document validation. The validation engine in
Integration Server validates the structure and content of a document (IData object) in the pipeline against an IS document type.
Pipeline validation. The validation engine in
Integration Server validates the structure and content of the pipeline against an IS document type.
XML validation. The validation engine in
Integration Server validates the structure and content of an XML document against an IS schema or IS document type.
For input/output, document, and pipeline validation, the blueprint used for data validation requires
constraints to be applied to its variables. Constraints are the restrictions on the structure or content of variables. Structural constraints specify the existence and structure of variables at run time. Content constraints describe the data type for a variable and the possible values for the variable at run time. For more information see,
About Variable Constraints.