When a CICS Web service is invoked in the atomic transaction pipeline, the SOAP message does not necessarily have to be part of an atomic transaction.
<soapenv:Header>
<wscoor:CoordinationContext soapenv:mustUnderstand="1"> 1
<wscoor:Expires>500</wscoor:Expires>
<wscoor:Identifier>com.ibm.ws.wstx:
0000010a2b5008c80000000200000019a75aab901a1758a4e40e2731c61192a10ad6e921
</wscoor:Identifier>
<wscoor:CoordinationType>http://schemas.xmlsoap.org/ws/2004/10/wsat</wscoor:CoordinationType> 2
<wscoor:RegistrationService 3
xmlns:wscoor="http://schemas.xmlsoap.org/ws/2004/10/wscoor">
<wsa:Address xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing">
http://clientIPaddress:clientPort/_IBMSYSAPP/wscoor/services/RegistrationCoordinatorPort
</wsa:Address>
<wsa:ReferenceProperties
xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing">
<websphere-wsat:txID
xmlns:websphere-wsat="http://wstx.Transaction.ws.ibm.com/extension">com.ibm.ws.wstx:
0000010a2b5008c80000000200000019a75aab901a1758a4e40e2731c61192a10ad6e921
</websphere-wsat:txID>
<websphere-wsat:instanceID
xmlns:websphere-wsat="http://wstx.Transaction.ws.ibm.com/extension">com.ibm.ws.wstx:
0000010a2b5008c80000000200000019a75aab901a1758a4e40e2731c61192a10ad6e921
</websphere-wsat:instanceID>
</wsa:ReferenceProperties>
</wscoor:RegistrationService>
</wscoor:CoordinationContext>
</soapenv:Header>