BPEL and WebService

Question

Hi, I'm a new guest here and I have a problem using BPEL 10.1.3.3. I work for HP now and I''ve updated the version of the application passing from BPEL 10.1.3.1 to BPEL 10.1.3.3. Running the project, when I want to create a task, it occurs a problem:
<WARN> <default.collaxa.cube.ws> <WSInvocationManager::Failed to get callback ServiceName in wsdl> Failed get wsdl service definition.
Failed to get a WSDL service that support the portType "{http://xmlns.oracle.com/pcbpel/taskservice/taskmanager}TaskManagerCallback" in WSDL definition "{http://xmlns.oracle.com/pcbpel/taskservice/taskmanager}TaskManager".
Please verify that WSDL portType "{http://xmlns.oracle.com/pcbpel/taskservice/taskmanager}TaskManagerCallback" is supported by a service in WSDL file.
and then other ERRORS:
<2008-04-08 10:36:14,683> <ERROR> <default.collaxa.cube.services> <PCException::<init>> Internal Error.
<2008-04-08 10:36:14,684> <ERROR> <default.collaxa.cube.services> <PCException::<init>> Internal error due to {0}.
<2008-04-08 10:36:14,685> <ERROR> <default.collaxa.cube.services> <PCException::<init>> Contact oracle support if error is not fixable.
<2008-04-08 10:36:14,686> <ERROR> <default.collaxa.cube.services> <PCException::<init>> Error in initiating task.
<2008-04-08 10:36:14,686> <ERROR> <default.collaxa.cube.services> <PCException::<init>> Error while initiating the task . The task is associated with the business process WFPlaylistWorking, identified by 70005
<2008-04-08 10:36:14,687> <ERROR> <default.collaxa.cube.services> <PCException::<init>> Check the error stack and fix the cause of the error. Contact oracle support if error is not fixable.
Please I need help. BPEL tecnology is new for me and then I don't know the answer.
My English is not perfect but I hope to explain myself good. Hi from Rome !!!

Answer 1

Hi Dharmendra,
I am trying to send a SOAP message from my BPEL process to a web service. I have a complete SOAP message in a complex variable defined in the wsdl for the partnerlink (web service). My problem is that when I invoke the partnerlink it fails even though the content shown in the BPEL console looks valid.
I have set up obtunnel to see what I am actually sending out from BPEL. You mention that BPEL creates the SOAP envelope automatically.
I think that my problem is a result of this automatic SOAP envelope that BPEL is creating. Do you know if there is a way to turn it off?
This is what I see in the TCP monitor, please note the double SOAP env:Body:
<env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <env:Body> <RCMR_IN000002NR01 xmlns="urn:hl7-org:v3" xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:wsa="http://www.w3.org/2005/08/addressing" xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd">
<env:Header>
<wsa:To xmlns:wsa="http://www.w3.org/2005/08/addressing">http://testhost/CCS/Service_Endpoint</wsa:To>
<wsa:From xmlns:wsa="http://www.w3.org/2005/08/addressing">
<wsa:Address>http://localhost/CCS/Service_Endpoint</wsa:Address>
<wsa:Metadata>
<device xmlns:hl7="urn:hl7-org:v3">
</device>
</wsa:Metadata>
</env:Header>
<env:Body>
<RCMR_IN000002NR01>
</RCMR_IN000002NR01>
</env:Body>
</RCMR_IN000002NR01>
</env:Body>
</env:Envelope>
Any help is appreciated.
Regards,
Aagaard
Edited by: Aagaard on Oct 30, 2008 8:59 PM
Should have mentioned. I am using BPEL 10.1.3.4
Edited by: Aagaard on Oct 31, 2008 8:43 AM
I have opened a new thread for this question so as to not confuse the issue more than necessary.
How many SOAP envelopes do you really need?