Is there a way to get SOAP header in bpel?

Question

Hi,
My web service returns a SessionID contained in the SOAP header. In Oracle PM, is there a way I could extract the SOAP header, or manipulate the SOAP header when invoking the web services? Any information would be appreciated.
Thanks!
Feng

Answer 1

Edwin,
I was trying your second approach, which utilizes the bpel extension to hold the header info, but with no luck.
The provided sample (Salesforce Flow) works well, and I can see the SOAP header using TCPMonitor. Then I created a simple echo service (using bpel) to replace the Salesforce.com Enterprise Web Services, and invoke the echo service from a bpel process with the same bpel extension. However, no header was sent out.
I guess there are something I was missing. Attached please find the wsdl file of the echo service, as well as the bpel files. Could you give me some idea what I did wrong? Or do you have any documentation about the bpel extensions?
Thanks a lot for the good support!
Feng
echo.wsdl
<?xml version="1.0"?>
<definitions name="echo"
targetNamespace="http://acm.org/samples"
xmlns:tns="http://acm.org/samples"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:plnk="http://schemas.xmlsoap.org/ws/2003/05/partner-link/"
xmlns="http://schemas.xmlsoap.org/wsdl/"
>
<!-- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
TYPE DEFINITION - List of types participating in this BPEL process
The BPEL Designer will generate default request and response types
but you can define or import any XML Schema type and use them as part
of the message types.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -->
<types>
<schema attributeFormDefault="qualified" elementFormDefault="qualified"
targetNamespace="http://acm.org/samples"
xmlns="http://www.w3.org/2001/XMLSchema">
<element name="echoRequest">
<complexType>
<sequence>
<element name="input" type="string"/>
</sequence>
</complexType>
</element>
<element name="echoResponse">
<complexType>
<sequence>
<element name="result" type="string"/>
</sequence>
</complexType>
</element>
<!-- Header Elements -->
<element name="SessionHeader">
<complexType>
<sequence>
<element name="sessionId" type="xsd:string"/>
<element name="InvokeID" type="xsd:string"/>
</sequence>
</complexType>
</element>
<element name="QueryOptions">
<complexType>
<sequence>
<element name="batchSize" type="xsd:int" />
</sequence>
</complexType>
</element>
<element name="SaveOptions">
<complexType>
<sequence>
<element name="autoAssign" type="xsd:boolean"/>
</sequence>
</complexType>
</element>
</schema>
</types>
<!-- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
MESSAGE TYPE DEFINITION - Definition of the message types used as
part of the port type defintions
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -->
<message name="echoRequestMessage">
<part name="payload" element="tns:echoRequest"/>
</message>
<message name="echoResponseMessage">
<part name="payload" element="tns:echoResponse"/>
</message>
<!-- Header Message -->
<message name="Header">
<part element="tns:SessionHeader" name="SessionHeader"/>
<part element="tns:SaveOptions" name="SaveOptions"/>
<part element="tns:QueryOptions" name="QueryOptions"/>
</message>
<!-- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
PORT TYPE DEFINITION - A port type groups a set of operations into
a logical service unit.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -->
<!-- portType implemented by the echo BPEL process -->
<portType name="echo">
<operation name="process">
<input message="tns:echoRequestMessage" />
<output message="tns:echoResponseMessage"/>
</operation>
</portType>
<!-- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
PARTNER LINK TYPE DEFINITION
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -->
<plnk:partnerLinkType name="echo">
<plnk:role name="echoProvider">
<plnk:portType name="tns:echo"/>
</plnk:role>
</plnk:partnerLinkType>
</definitions>
echo.bpel
<!-- echo BPEL Process [Generated by the Oracle BPEL Designer] -->
<process name="echo" targetNamespace="http://acm.org/samples" suppressJoinFailure="yes" xmlns:tns="http://acm.org/samples" xmlns="http://schemas.xmlsoap.org/ws/2003/03/business-process/" xmlns:bpelx="http://schemas.oracle.com/bpel/extension" xmlns:ora="http://schemas.oracle.com/xpath/extension" xmlns:cx="http://schemas.collaxa.com/xpath/extension">
     <!-- ================================================================= -->
     <!-- PARTNERLINKS -->
     <!-- List of services participating in this BPEL process -->
     <!-- ================================================================= -->
     <partnerLinks>
          <!-- The 'client' role represents the requester of this service. -->
          <partnerLink name="client" partnerLinkType="tns:echo" myRole="echoProvider"/>
     </partnerLinks>
     <!-- ================================================================= -->
     <!-- VARIABLES -->
     <!-- List of messages and XML documents used within this BPEL process -->
     <!-- ================================================================= -->
     <variables>
          <!-- Reference to the message passed as input during initiation -->
          <variable name="input" messageType="tns:echoRequestMessage"/>
          <!--
Reference to the message that will be returned to the requester
-->
          <variable name="output" messageType="tns:echoResponseMessage"/>
     </variables>
     <!-- ================================================================= -->
     <!-- ORCHESTRATION LOGIC -->
     <!-- Set of activities coordinating the flow of messages across the -->
     <!-- services integrated within this business process -->
     <!-- ================================================================= -->
     <sequence name="main">
          <!-- Receive input from requester.
Note: This maps to operation defined in echo.wsdl
-->
          <receive name="receiveInput" partnerLink="client" portType="tns:echo" operation="process" variable="input" createInstance="yes"/>
          <!-- Generate reply to synchronous request -->
          <assign>
               <copy>
                    <from expression="concat('echo: ', bpws:getVariableData(&quot;input&quot;, &quot;payload&quot;, &quot;/tns:echoRequest/tns:input&quot;))">
                    </from>
                    <to variable="output" part="payload" query="/tns:echoResponse/tns:result"/>
               </copy>
          </assign>
          <reply name="replyOutput" partnerLink="client" portType="tns:echo" operation="process" variable="output"/>
     </sequence>
</process>
bpel process that invokes the echo service
<!-- testHeader6 BPEL Process [Generated by the Oracle BPEL Designer] -->
<process name="testHeader6" targetNamespace="http://acm.org/samples" suppressJoinFailure="yes" xmlns:tns="http://acm.org/samples" xmlns="http://schemas.xmlsoap.org/ws/2003/03/business-process/" xmlns:bpelx="http://schemas.oracle.com/bpel/extension" xmlns:ora="http://schemas.oracle.com/xpath/extension" xmlns:cx="http://schemas.collaxa.com/xpath/extension">
     <!-- ================================================================= -->
     <!-- PARTNERLINKS -->
     <!-- List of services participating in this BPEL process -->
     <!-- ================================================================= -->
     <partnerLinks>
          <!-- The 'client' role represents the requester of this service. -->
          <partnerLink name="client" partnerLinkType="tns:testHeader6" myRole="testHeader6Provider"/>
          <partnerLink name="echo" partnerLinkType="tns:echo" partnerRole="echoProvider"/>
     </partnerLinks>
     <!-- ================================================================= -->
     <!-- VARIABLES -->
     <!-- List of messages and XML documents used within this BPEL process -->
     <!-- ================================================================= -->
     <variables>
          <!-- Reference to the message passed as input during initiation -->
          <variable name="input" messageType="tns:testHeader6RequestMessage"/>
          <!--
Reference to the message that will be returned to the requester
-->
          <variable name="output" messageType="tns:testHeader6ResponseMessage"/>
          <variable messageType="tns:echoRequestMessage" name="i2"/>
          <variable messageType="tns:echoResponseMessage" name="o2"/>
          <variable name="header" messageType="tns:Header"/>
     </variables>
     <!-- ================================================================= -->
     <!-- ORCHESTRATION LOGIC -->
     <!-- Set of activities coordinating the flow of messages across the -->
     <!-- services integrated within this business process -->
     <!-- ================================================================= -->
     <sequence name="main">
          <!-- Receive input from requester.
Note: This maps to operation defined in testHeader6.wsdl
-->
          <receive name="receiveInput" partnerLink="client" portType="tns:testHeader6" operation="process" variable="input" createInstance="yes"/>
          <!-- Generate reply to synchronous request -->
          <assign>
               <copy>
                    <from expression="12345">
                    </from>
                    <to variable="i2" part="payload" query="/tns:echoRequest/tns:input"/>
               </copy>
               <copy>
                    <from expression="1111">
                    </from>
                    <to variable="header" part="SessionHeader" query="/tns:SessionHeader/tns:sessionId"/>
               </copy>
          </assign>
          <invoke partnerLink="echo" portType="tns:echo" operation="process" inputVariable="i2" bpelx:inputHeaderVariable="header" outputVariable="o2"/>
          <reply name="replyOutput" partnerLink="client" portType="tns:testHeader6" operation="process" variable="output"/>
     </sequence>
</process>