XML domain message flows

If you are not using the SOAP domain then your message flow needs to take account of the actual bitstream format of the Web service messages you are working with. A different logical tree format is used by each domain.

If the messages are SOAP then you can use either the XMLNSC domain or the MRM XML domain. Both domains offer validation. The XMLNSC domain is more efficient, whilst the MRM XML domain can be useful if you have specific message transformation requirements, for example, if your message flow also uses binary data formats.

If the messages use MIME (for example, SOAP with Attachments or MTOM) you can use the MIME domain. In this case your message flow will probably also need to identify at least the MIME part corresponding to the SOAP payload and then explicitly parse this using the XMLNSC or MRM domain as above.

In the SOAP domain, WSDL is used to automatically configure your nodes with the appropriate endpoint information. If you are not using the SOAP domain, then you must select and configure the transport nodes manually. Typical WSDL bindings would be:

You can configure message flows that receive input messages from clients using one transport, and interact with a Web service or legacy application using another.

You can propagate a message to more than one location. For example, the Web service response to be returned to a client by an HTTPReply node might first be sent to an auditing application using an MQOutput node, after making any required adjustments to the message headers.

Nodes are used together in the following basic patterns, using HTTP nodes as example transports:

If required, the SOAPExtract and SOAPEnvelope nodes can be used in conjunction with these patterns to respectively extract the SOAP payload and rebuild a SOAP Envelope.

If you want your message flow to validate messages, then an appropriate message set must be deployed with the flow. An appropriate message set is created either by importing existing WSDL or by generating WSDL from an existing message set. For details about importing existing WSDL, see Importing from WSDL. For details about generating WSDL from an existing message set, see WSDL generation.

You can also create a new message set and flow based on existing WSDL or XSD files. For details, see Creating an application based on WSDL or XSD files

The generated message set will contain message definitions for the relevant SOAP Envelope version and for the XML payload data defined by the WSDL. In the XMLNSC or MRM XML domains, messages can be validated against the message set. For details, see Validating messages.

Related concepts
WebSphere MQ Web Services Transport
Generate WSDL
Message flows overview
Related tasks
Developing message flows
Deploying
Related reference
Built-in nodes
Notices | Trademarks | Downloads | Library | Support | Feedback

Copyright IBM Corporation 1999, 2009Copyright IBM Corporation 1999, 2009.
Last updated : 2009-01-07 15:20:38

ac34520_