SOAP Fault TIBCO BusinessConnect SOAP Protocol supports SOAP fault in both versions 1.1 and 1.2. For inbound messages, when an exception or error occurs, TIBCO BusinessConnect SOAP Protocol generates a SOAP fault in the same version as the incoming message, and sends back the SOAP fault to the trading partner. For TIBCO BusinessConnect SOAP Protocol, the TIBCO ActiveMatrix BusinessWorks private process supports the SOAP fault only in version 1.2. • On BusinessConnect responder side, when an error occurs in the back office system, a SOAP fault is sent back. The responder private process implemented by TIBCO ActiveMatrix BusinessWorks only supports sending version 1.2 SOAP fault to the responder BusinessConnect server, regardless of the SOAP version of the original request message. If the original request message is a version 1.1 SOAP message, the responder BusinessConnect server converts the version 1.2 SOAP fault into a version 1.1 SOAP fault and sends it back to the initiator. Because of the different fault structure in versions 1.1 and 1.2, only the first one of the fault reasons in version 1.2 is extracted and used in the version 1.1 SOAP fault. • On BusinessConnect initiator side, if the initiator receives a SOAP version 1.1 fault for whatever reason, BusinessConnect server converts this SOAP fault to version 1.2 before it is forwarded to the private process. For TIBCO BusinessConnect SOAP Protocol, the TIBCO ActiveMatrix BusinessWorks private process only supports SOAP fault in version 1.2 with BusinessConnect. If you want to use SOAP fault in version 1.1, you must do the convertion yourself. If you use TIBCO ActiveMatrix BusinessWorks to convert when you send a SOAP fault, perform the following steps: 1. Populate the value in the soapFault > Code > Value field as your faultCode. 2. Populate the value in the soapFault > Reason > ReasonText > content field as your faultString. 3. Populate the value in the soapFault > Role field as your faultActor. After performing these steps, the SOAP fault you send from TIBCO ActiveMatrix BusinessWorks private process to BusinessConnect is in version 1.2. BusinessConnect automatically converts the SOAP fault back to version 1.1 before the SOAP fault is sent to a trading partner if the trading partner wants the SOAP fault in version 1.1. Sample of a SOAPFault in Version 1.1 <SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"> <SOAP-ENV:Body> <SOAP-ENV:Fault> <faultcode>SOAP-ENV:Server</faultcode> <faultstring>Server Error</faultstring> <faultactor>SOAPClient</faultactor> <detail> <ei:ErrorInfo xmlns:ei="http://www.tibco.com/ namespaces/bc/2002/04/errorinfo.xsd"> <code>922</code> <description>Actual error from schema validation</description> </ei:ErrorInfo> </detail> </SOAP-ENV:Fault> </SOAP-ENV:Body> </SOAP-ENV:Envelope> Sample of a SOAPFault in Version 1.2 <env:Envelope xmlns:env="http://www.w3.org/2003/05/soap-envelope" xmlns:m="http://www.example.org/timeouts" xmlns:xml="http://www.w3.org/XML/1998/namespace"> <env:Body> <env:Fault> <env:Code> <env:Value>env:Sender</env:Value> <env:Subcode> <env:Value>m:MessageTimeout</env:Value> </env:Subcode> </env:Code> <env:Reason> <env:Text xml:lang="en">Sender Timeout</env:Text> </env:Reason> <env:Detail> <m:MaxTime>P5M</m:MaxTime> </env:Detail> </env:Fault> </env:Body> </env:Envelope>