IBM Support

IA9A: WITHDRAWN: WebSphere Message Broker - XML Validator Plug-in Node



This SupportPac supplies a WebSphere Message Broker plug-in node that validates an XML message against an XML schema.

Download Description

This SupportPac is now withdrawn and will be archived in April 2020.
This SupportPac supplies a WebSphere Message Broker plug-in node that validates an XML message against an XML schema. If the message conforms to the schema, the message is passed to the Out terminal unchanged. However, if errors are encountered these are added to the Environment tree, and passed to the Invalid terminal, along with the unchanged message.

The XML Validator node checks the bitstream of a message, as opposed to the logical structure, and therefore supports any message format, e.g. XML, XMLNS, BLOB etc. Configurable parameters are supplied to allow the schema defined in the XML document to be overridden, and can be set either through the node properties or at run time, by the use of Environment/LocalEnvironment variables.

The node is implemented as a Java plug-in, and supports all Message Broker platforms except z/OS.

Possible Uses
This SupportPac could be used as part of a web services message flow, if there is a requirement to validate incoming, or outgoing, XML messages against schemas. The ability to validate against a different schema for each message enables the node to be used in situations where there are a large variety of messages passing through the flow. For instance, if the broker is acting as a web services intermediary, several types of messages could be validated by one message flow using this node.

It is also useful when the content of a schema changes frequently, such as during application development stages, as no re-deploy of the message flow is required to use the changed schema.

The plug-in node could also be used to check messages against schemas for message flows that only use the XML or XMLNS domains.

New in this Release
• Updated for WebSphere Message Broker v7.

Skill Level Required
Installation and use of WebSphere Message Broker.

Author: Mark Frost, WebSphere Message Broker Development, Hursley
Category: 2
Released: 03May05
Last updated: 07Jul10
Current Version: 1.1
»Please note that the version number shown in the right-hand pane is the version of the WebSphere MQ or WebSphere MB product that this SupportPac applies to. The date is the last webpage refresh.

To view the complete portfolio of WebSphere MQ SupportPacs please visit the WebSphere MQ SupportPacs homepage.


This SupportPac requires:
WebSphere Message Broker V5, V6 or V7

Installation Instructions

To install the SupportPac:

• Download into a temporary directory
• Uncompress using InfoZip's Unzip. This will create the necessary files, after which you may delete
• Follow the installation instructions provided in the ia9a.pdf document

[{"INLabel":"ia9a.pdf","INLang":"US English","INSize":"366818","INURL":""}]
[{"DNLabel":"","DNDate":"07/07/2010","DNLang":"US English","DNSize":"548309","DNPlat":{"label":"AIX","code":"PF002"},"DNURL":"","DNURL_FTP":" ","DDURL":null}]

Technical Support

Category 2 SupportPacs are provided in good faith and AS-IS. There is no warranty or further service implied or committed and any supplied sample code is not supported via IBM product service channels.

You may submit a question using the 'rate this page' below but a response is not guaranteed.

Please read the license information contained within the zip file of this SupportPac to determine if you want to use it.

[{"Product":{"code":"SSKM8N","label":"WebSphere Message Broker"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Component":"SupportPac","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF010","label":"HP-UX"},{"code":"PF016","label":"Linux"},{"code":"PF012","label":"IBM i"},{"code":"PF027","label":"Solaris"},{"code":"PF025","label":"Platform Independent"},{"code":"PF033","label":"Windows"}],"Version":"7.0;6.0;5.0","Edition":"","Line of Business":{"code":"LOB15","label":"Integration"}}]

Document Information

Modified date:
13 January 2020