About Run-Time Validation for a Published Document
In a publish-and-subscribe solution, Integration Server validates a published document against the associated publishable document type. Validation occurs immediately after the publishing service executes. If Integration Server determines that the published document is invalid (that is, the published document does not conform to the associated publishable document type), the publishing service returns a service exception that indicates the validation error. Integration Server does not publish the document.
While document validation ensures that document subscribers receive valid documents only, it can be an expensive operation in terms of resources and performance. In some situations, you might not want to validate the published document. For example, you might want to disable document validation when publishing documents that were already validated. Suppose that a back-end resource, created and validated the document and then sent it to Integration Server. If Integration Server in turn, publishes the document to Broker, you might not need to validate the document when publishing it because it was already validated by the back-end resource. You might also want to disable all document validation when publishing native Broker events.
Integration Server provides two settings that you can use to configure validation for published documents.
A global setting named watt.server.publish.validateOnIS that indicates whether
Integration Server always performs validation, never performs validation, or performs validation on a per document type basis. You can set this property using
Integration Server Administrator. For more information about setting this property, see
webMethods Integration Server Administrator’s Guide.
A
webMethods messaging property for publishable document types that indicates whether instances of a publishable document type should be validated.
Integration Server honors the value of this property (named
Validate when published) only if the watt.server.publish.validateOnIS is set to
perDoc (the default).
Note:
When deciding whether to disable document validation, be sure to weigh the advantages of a possible increase in performance against the risks of publishing, routing, and processing invalid documents.