If a broker is to communicate with an existing web service, it typically needs to send and receive SOAP messages. To use this approach you should use the MRM domain. You will need to ensure that the broker's message model and the WSDL definition used by the web service describe the same messages. In general this is achieved by importing the WSDL for the existing web service using the broker tooling. Currently only WSDL version 1.1 is supported.
Only the WSDL operation, message and part definitions will be represented in the resulting broker model. Starting with the lowest level, a WSDL definition describes:
The resulting model allows the user to parse incoming SOAP messages using the MRM XML parser where the message type would be Envelope. The message model for the SOAP envelope defines the outer SOAP wrapper with its constituent Header and Body sections and a number of attachment points where the various business payloads can appear. These attachment points are defined with composition message, allowing the broker messages created by the WSDL importer to appear at these points.
The allowed attachment points are Envelope.Body, Envelope.Header and Envelope.Body.Fault.detail. A message from the user's message model may appear at each point (in the case of the Envelope.Header, multiple messages may appear). In the case of rpc-style WSDL, the message expected at Envelope.Body is the automatically generated message corresponding to the WSDL operation. In all other cases the messages expected are those defined by the WSDL message parts for each operation.