Parsing and Building SOAP Messages
This section explains how to use the SOAP functions to parse information from incoming requests, and to construct outgoing messages (responses and requests) in your rules and rule functions.
This manual does not explain how to work with the SOAP protocol. For example, you should understand how the Actor and MustUnderstand attributes in SOAP headers are used to process the message as it passes from its originator, through intermediary applications, to its ultimate destination.
- Working with Incoming SOAP Messages (Event Payloads)
An incoming SOAP message can be a request, or a response, depending on whether TIBCO BusinessEvents is acting as the server or the client. TIBCO BusinessEvents can also act as an intermediate node along the path of a SOAP message to its ultimate destination. This section explains how to parse information out of the incoming event payload, which contains the SOAP message. - Parsing (and Optionally Removing) Headers and Header Attributes
- Parsing the SOAP Body (SOAPBodyParts)
Two functions are available for getting SOAP body parts. - Parsing Attachments
The following functions enable you to work with SOAP attachments in the request message: - Parsing SOAP Fault XML Nodes
The following functions enable you to work with the standard SOAP Fault XML nodes from the payload of a SOAP event: - Working with Outgoing SOAP Messages (Event Payloads)
You can add header parts, body parts, fault parts and attachments to the outgoing SOAP message (whether it is a response or a request).
Copyright © TIBCO Software Inc. All rights reserved.