When you use the MQ/JMS binding as the transport protocol, you choose the default SOAP data handler (SOAPDataTransformationConfig) to parse the SOAP message. However, the business object in the SOAP header is not parsed. Also, if there are multiple business objects in the SOAP body, only the first business object is parsed.
The business object in the SOAP header is not parsed and multiple business objects in the SOAP body are not parsed.
Resolving the problem
You can resolve this issue by implementing a customized SOAP data handler. For information on how to implement a customized SOAP data handler, see the Data handlers topic in the WebSphere Process Server Information Center.