Understanding Message Schema Validation
PeopleSoft Integration Broker enables you to validate, at runtime, the messages defined in service operations against message schemas.
Validating messages against message schemas can ensure that during integration development no changes or deletions were inadvertently made to a message. You can use schema validation on outbound and inbound messages.
During runtime schema validation, PeopleSoft Integration Broker checks messages to ensure that the XML structure is valid according to the specified message schema. If Integration Broker encounters a service operation with a message structure that does not adhere to the specified message schema, message delivery fails and Integration Broker generates an error message.
Schema validation is based on the message schema for the message.version defined on the default service operation.
You can view any schema validation error details on the source application server, using the Asynchronous Details page or Synchronous Details page in the Service Operations Monitor.
When schema validation is enabled the structure of a message cannot be changed.
In instances where an inbound transaction has a transformation applied, the input message.version is used for schema validation. If an input message.version is not defined, then validation takes place using the request message.version of the default service operation.
For the case where a point-to-point routing and an any-to-local routing are both defined, the system uses the point-to-point routing to check for a transform.
PeopleSoft Integration Broker does not perform parser validation on part messages in container messages.
URLs defined in container messages do not contain absolute paths. As a result, the parser cannot import these schemas to perform validation.
PeopleSoft internal validation is performed on the data and structure of part messages within contain messages. However, these validation results may be different than results achieved using parser validation.