Mediation Module - SOAP Headers

My Mediation Flow is exposed as a WSDL.  I am having issues in adding SOAP
Headers to the SOAP Requests that I send to this mediation module.  <br
/>
<br />
I am sending a SOAP Request with some custom headers added to SOAP Headers. 
However, when I transform the ServiceMessageObject to XML, I donot see any SOAP
Header available in the SMO.  Do I need to enable something in my Mediation Flow
to accept SOAP Headers?<br />
<br />
Thanks,<br />

My understanding is that when an SMO comes out of the Mediation Flow and arrives
at an SCA Import Component then if the Import is Web Services bound, the SOAP
message generated (and then sent) will be based upon the content of the SMO
structure.  What this means is that the SMO structure is designed to be used by
the Import component.    When you say that you turn the SMO into XML ... is this
being done inside your Mediation Flow?  In which case I wouldn't expect to see a
SOAP data appearing but an SMO XML document instead.<br />
<br />

Here  is how my flow is implemented:<br />
<br />
Export---Mediation Flow<br />
<br />
The custom mediation is exported as a WSDL binding to the outside world
(Export).  I generated a WSDL out of this flow and provided to various clients
(J2EE and non-j2ee).  Clients create SOAP message complaint to the above WSDL
with some SOAP Headers appended to the requests.<br />
<br />
My Mediation Flow has a custom Mediation primitve that deserializes the SMO
object (using BOXMLSerializer).  When I SYS OUT (print) the SMO, I donot see
SOAP Headers in SMO.<br />
Hope this gives you an idea.<br />
<br />
Thanks,<br />

Thanks ... that really, really helped.   The next thing I would do is to
"intercept" the SOAP/HTTP message that is being sent from the Web
Service (WS) client and dump the SOAP-XML data.  You can use the TCP Monitor
capability of WID to do this.  Assuming that your Web Service is listening on
port 9080 (example) then you can setup the TCP Monitor to listen on port 9280
and forward traffic to 9080.  You then change the endpoint information for the
clients to point to 9280.  This will then allow the SOAP XML data that is
physically transmitted over the wire to be seen.  What I would then do is to
post back with attachments containing:<br />
<br />
1) The SOAP-XML data that has been ACTUALLY sent to WPS<br />
2) The output in the console of the BOXMLSerializer generated XML<br />
<br />

It finally worked.  <br />
<br />
For everybody's benefit:<br />
<br />
What is missing in my module is defining a Business Object with the necessary
structure (Custom SOAP Header structure). <br />
<br />
please see the below link:<br />
<br />
<a class="jive-link-external"
href="http://www.ibm.com/developerworks/webservices/library/ws-soapheaders/
index.html">http://www.ibm.com/developerworks/webservices/library/ws-soa
pheaders/index.html</a><br />
<br />
Thanks,<br />