Start of change

Determining if the SOAP message is part of an atomic transaction

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.

The <soapenv:Header> element contains specific information when the SOAP message is part of an atomic transaction. To find out if the SOAP message is part of an atomic transaction, you can either:
The following example shows the information that you could see in the SOAP envelope header for 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>
  1. The CoordinationContext indicates that the SOAP message is intended to participate in an atomic transaction. It contains the necessary information for the Web service provider to be part of the coordination service, assuming that the provider is configured to recognize and process the header.
  2. The CoordinationType indicates the version of the WS-AT specification that the coordination context complies with.
  3. The coordination RegistrationService describes where the coordinators registration point is, and the information that the participating Web service must return to the coordinator when it attempts to register as a component of the atomic transaction.
End of change