NonStop SOAP User's Manual

Using NonStop SOAP with a TS/MP Application and
NonStop Processes
NonStop SOAP User’s Manual—520501-012
6-42
Controlling the Output Encoding
Requests to Commit the Transaction and End the Session
This following request commits the transaction and end the subsession:
<SOAP-ENV:Envelope
xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">
<SOAP-ENV:Header>
<Id:Session SessionID="QK797dd69023"
CurrentTransactionCommand="End"
SessionCommand="AbortSubsession"
xmlns:Id="urn:compaq_nsk_oss_SoapHeader"/>
</SOAP-ENV:Header>
<SOAP-ENV:Body>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
This request ends the session:
<SOAP-ENV:Envelope
xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">
<SOAP-ENV:Header>
<Id:Session SessionID="QK797dd69023"
SessionCommand="AbortSubsession"
xmlns:Id="urn:compaq_nsk_oss_SoapHeader"/>
</SOAP-ENV:Header>
<SOAP-ENV:Body>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
Controlling the Output Encoding
NonStop SOAP supports all encodings supported by the ICU library (version 2.6.1)
included in NonStop XML. The encoding of the incoming request to NonStop SOAP
can be different from the encoding of the response generated by NonStop SOAP.
If the target TS/MP service or NonStop process supports multibyte characters (as
indicated by the SrvrEncoding attribute in the SDL file), the encoded request data is
converted to data with an encoding understood by the target service. If the target
service does not support multibyte characters, the encoded request data is converted
to data with UTF-8 encoding.
NonStop SOAP lets you control the output encoding for all responses from a service or
for an individual request: