SOAP fault information. Some of the attributes in the SOAP header block are: env:role: The "role" attribute is used to identify the role of the specific target associated with the header block. This role can be standard roles or custom roles, and the absence of a role indicates that the role will be the final destination. env:mustUnderstand: The "mustUnderstand" attribute is used to specify the header block needing to be processed. It is more of a Boolean variable and can have a value of either "true" or "false." If the value of "mustUnder- stand" is true, then destination node must process the header block. If there is an issue during the processing or the processing of the header block fails, then a fault event has to be generated. If the value of "mustUnderstand" is XML-Based Protocols false then the destination node may or may not process the header block. If this attribute is not present in the header block attribute then it is equiva- lent to setting the attribute to false. As discussed earlier the header block is not mandatory, but there could be critical information at times in the header specific for an application. In these scenarios, setting the attribute value as true will ensure that the header block is processed as required for the application. env:relay: Control of header blocks during a relay operation can be done with the "relay" attribute. Not all header blocks will be processed by intermediary nodes and default behavior is to remove the header before a relay operation. So unnecessary propagation of header blocks can be avoided and maintaining of specific headers can be done using the relay attribute. It is a feature that is newly introduced in SOAP 1.2. SOAP fault as defined with the tag <env:Fault> and can be used to carry error and status information. The fault information will contain the identifier or group to which the fault message belongs (tag: <faultcode>), the short description of the fault (tag: <faultstring>), the node or actor associated with the fault (tag: <faultac- tor>), and det