Summary

The data type of a SOAP header in a SOAP message generated or processed by a SOAP or .NET connector is an element: an instance of the W3C DOM object org.w3c.dom.Element.

The value of a SOAP header must be well-formed, namespace-qualified XML. When data mapping a SOAP header in a response message (Map To), the data must be processed by an XML parse rule. However, if the XML data for an outgoing SOAP header is simple (Map From), you may be able to provide the data from a Property-Set step in the connector activity rather than from an XML stream rule.

Suggested Approach

Map From

How you map the XML data for a SOAP header depends on the data. Does the data contain a single element with a constant value? Does the data contain complex types or embedded elements?

If the data for the header is complex (that is, it contains more than one element), use an XML stream rule to provide the value. For information about using XML stream rules, see the document Data Mapping XML, located on the Integration pages. (See Data Mapping XML V5. )

If the data contains a single element with a constant value, you may be able to configure a step in the connector activity that sets the XML for the header to a single value text property. Then you create a data mapping on the connector rule’s Request tab that maps the value for the header from that property.

For example, perhaps the connector needs to include a WS-Security MessageID header in the request. The connector activity could use a Property-Set method to set the following into a property named RequestMessageID:

“<wsa:MessageID xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing">12345</wsa:MessageID>”

Then, you could map the value of the wsa:MessageID SOAP header from the RequestMessageID property in the connector rule.

Map To

When mapping an incoming SOAP header, you can either map it directly to an XML parse rule or map it to a single value string property and then call the parse rule from the connector activity. For information about using XML parse rules, see the document Data Mapping XML, located on the Integration pages. (See Data Mapping XML V5. )