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.
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.
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.