IBM BPM, V8.0.1, All platforms > Get started with IBM BPM > Key concepts > Bindings > Binding types > Web service bindings

Transport header propagation

When handling SOAP messages, you might need to access information from certain transport headers in messages that are received, ensure that messages with transport headers are sent with specific values, or allow transport headers to pass across a module.

When you configure a web service binding in Integration Designer, you can indicate that you want transport headers to be propagated.


Specifying propagation of headers

To configure the propagation of transport headers for an import or export...

  1. From the Properties view of Integration Designer, select Binding > Propagation.
  2. Set the transport header propagation option that you require.

Transport header propagation is disabled by default and can be deployed only to a Version 7.0.0.3 (or later) runtime environment. Also note that, for Version 7.0.0.3, transport header propagation is limited to HTTP transport headers only.

If you enable propagation of transport headers, the headers will be propagated across a module from received messages and, if you do not explicitly remove the headers, the headers will be used in subsequent invocations in the same thread.

Transport headers cannot be propagated when you are using the web service (JAX-RPC) binding.


Access the header information

When transport header propagation is enabled for received messages, all transport headers (including customer-defined headers) are visible in the service message object (SMO). You can set the headers to different values or create new ones. If , however, that there is no checking or validation of the values you set, and any improper or incorrect headers might cause web service runtime problems.

Consider the following information about the setting of HTTP headers:

You can access the header information in one of the following ways:


Troubleshooting

If you encounter problems when sending the revised headers, you can intercept the TCP/IP message by using tools such as the TCP/IP Monitor in Integration Designer. You access the TCP/IP Monitor by selecting Run/Debug > TCP/IP Monitor from the Preferences page.

You can also view the header values using the JAX-WS engine trace: org.apache.axis2.*=all: com.ibm.ws.websvcs.*=all:

Web service bindings


Related concepts:
Protocol header propagation from non-SCA export bindings


Related information:
SMO: HTTP schema
HTTP Header Setter mediation primitive
Code to access binding-specific headers
Binding-specific headers in a Service Message Object (SMO)