Support for WSDL 1.1 header mapping into message parts in Designer

what exactly does this do?

Sometimes services expect some information to be provided in the SOAP header instead of the SOAP body.
In a BPEL process, you don't have access to the SOAP envelope. You only have access to a message variable that carries the information to be passed in the SOAP message. However, messages can have multiple parts, and in the WSDL definition of the service, the binding section allows to bind a specific part to the SOAP header. This way, from BPEL you can assign data to a message part that will be automatically put into the SOAP header based on the SOAP binding.
This is not supported currently in Intalio|BPMS Server. The goal of this project is to add that capability.

JAG, you mean that even if we modify the SOAP binding and the generated BPEL to assign such header variables, it won't run on ODE ?
Any workaround this limitation in Intalio Server ?

Cheers

Yes, because you can't change BPEL to access SOAP header, because BPEL has no clue about SOAP. BPEL only deals with variables, which have XML structures. The SOAP envelope is an implementation detail of the underlying transport infrastructure. BPEL is a layer above.
So when you want to provide information from your process that needs to be put in the SOAP header, you need to put this information in a message part that is bound to the SOAP header. This binding is not defined in the BPEL code, but in the WSDL.
Today, even if you change the binding in the WSDL, it won't work because the Server does not support such binding. This feature is about supporting this binding.
The good news is that this feature has now been funded by a customer and will be available in 5.0 to everyone.

Hello,

Support for SOAP header mapping is complete and is now part of Intalio|BPMS 5.2 (Community and Enterprise Editions).

Documentation and samples can be found on the Intalio Support Wiki.

Thanks,

Shao.