Unable to invoke Webservice with BPEL process

Hi,
I wrote a basic WebService in Java and now I want to invoke it with a simple BPEL Process. But it doesn't work. I am using Netbeans 6.5 as IDE and GlassFish V2 as Server.
Everytime when I try to test my BPEL Process, I got back the following failure message:
ERROR: Successful execution of Start: NPSProcesstestingApp
WARNING: (JBIMA0405) Start of service assembly NPSProcesstestingApp succeeded partially; some service units failed to start.
* Component: sun-http-binding
ERROR: (SOAPBC_START_1) HTTPBC-E00205: Start failed. java.lang.Exception: LifecycleException: PWC3985: Initialisierung der Protokoll-Behandlungsroutine fehlgeschlagen: java.net.BindException: Address already in use: bind: 8083
* Component: sun-bpel-engine
INFO: (JBIMA0409) Lifecycle operation start succeeded for Service Unit NPSProcesstestingApp-NPSProcesstesting.
I have absolutely no idea why it doesn't work, my webservice is running on localhost at port 8083: http://localhost:8083/numberportingservice, and I deploy it in the following way:
//NumberPortingService
NumberPortingServiceImpl npsImpl = new NumberPortingServiceImpl();
new TestDataGeneratorNPS(npsImpl);
JaxWsServerFactoryBean sfNPS = new JaxWsServerFactoryBean();
sfNPS.setServiceClass(NumberPortingService.class);
sfNPS.setAddress("http://localhost:8083/numberportingservice");
sfNPS.setServiceBean(npsImpl);
sfNPS.create();
That works fine, but it doesn't work with the BPEL process, GlassFish is running on Port 7272 and my webservice on Port 8083, so is the Port 8083 blocked? I checked it, it is not blocked by another application, only my webservice is using it.
My BPEL Process looks like this:
<?xml version="1.0" encoding="UTF-8"?>
<process
name="NPStesting"
targetNamespace="http://enterprise.netbeans.org/bpel/NPSProcesstesting/NPStesting"
xmlns="http://docs.oasis-open.org/wsbpel/2.0/process/executable"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:sxt="http://www.sun.com/wsbpel/2.0/process/executable/SUNExtension/Trace"
xmlns:sxed="http://www.sun.com/wsbpel/2.0/process/executable/SUNExtension/Editor"
xmlns:tns="http://enterprise.netbeans.org/bpel/NPSProcesstesting/NPStesting">
<import namespace="http://enterprise.netbeans.org/bpel/numberportingserviceWrapper" location="localhost_8083/numberportingserviceWrapper.wsdl" importType="http://schemas.xmlsoap.org/wsdl/"/>
<import namespace="http://jaxws/" location="localhost_8083/numberportingservice.wsdl" importType="http://schemas.xmlsoap.org/wsdl/"/>
<partnerLinks>
<partnerLink name="PartnerLink1" xmlns:tns="http://enterprise.netbeans.org/bpel/numberportingserviceWrapper" partnerLinkType="tns:NumberPortingServiceLinkType" myRole="NumberPortingServiceRole"/>
</partnerLinks>
<variables>
<variable name="StatecountOut" xmlns:tns="http://jaxws/" messageType="tns:statecountResponse"/>
<variable name="StatecountIn" xmlns:tns="http://jaxws/" messageType="tns:statecount"/>
</variables>
<sequence>
<receive name="Receive1" createInstance="yes" partnerLink="PartnerLink1" operation="statecount" xmlns:tns="http://jaxws/" portType="tns:NumberPortingService" variable="StatecountIn"/>
<reply name="Reply1" partnerLink="PartnerLink1" operation="statecount" xmlns:tns="http://jaxws/" portType="tns:NumberPortingService" variable="StatecountOut"/>
</sequence>
</process>
The wsdl of my webservice looks like this:
<?xml version='1.0' encoding='UTF-8'?><wsdl:definitions name="NumberPortingServiceService" targetNamespace="http://jaxws/" xmlns:ns1="http://schemas.xmlsoap.org/soap/http" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:tns="http://jaxws/" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<wsdl:types>
<xs:schema attributeFormDefault="unqualified" elementFormDefault="unqualified" targetNamespace="http://jaxws/" xmlns:tns="http://jaxws/" xmlns:xs="http://www.w3.org/2001/XMLSchema">
<xs:element name="address" type="tns:address" />
<xs:element name="check_porting_possible" type="tns:check_porting_possible" />
<xs:element name="check_porting_possibleResponse" type="tns:check_porting_possibleResponse" />
<xs:element name="check_porting_status" type="tns:check_porting_status" />
<xs:element name="check_porting_statusResponse" type="tns:check_porting_statusResponse" />
<xs:element name="customer" type="tns:customer" />
<xs:element name="customers" type="tns:customers" />
<xs:element name="get_porting_result" type="tns:get_porting_result" />
<xs:element name="get_porting_resultResponse" type="tns:get_porting_resultResponse" />
<xs:element name="portingRequest" type="tns:portingRequest" />
<xs:element name="portingResult" type="tns:portingResult" />
<xs:element name="schedule_batch_porting" type="tns:schedule_batch_porting" />
<xs:element name="schedule_batch_portingResponse" type="tns:schedule_batch_portingResponse" />
<xs:element name="statecount" type="tns:statecount" />
<xs:element name="statecountResponse" type="tns:statecountResponse" />
<xs:element name="telephoneNumber" type="tns:telephoneNumber" />
<xs:complexType name="check_porting_possible">
<xs:sequence>
<xs:element minOccurs="0" name="customer" type="tns:customer" />
<xs:element name="providerId" type="xs:long" />
</xs:sequence>
</xs:complexType>
<xs:complexType name="customer">
<xs:sequence>
<xs:element minOccurs="0" name="id" type="xs:string" />
<xs:element minOccurs="0" name="name" type="xs:string" />
<xs:element name="provider" type="xs:long" />
<xs:element minOccurs="0" name="address" type="tns:address" />
<xs:element minOccurs="0" name="telephoneNumber" type="tns:telephoneNumber" />
</xs:sequence>
</xs:complexType>
<xs:complexType name="address">
<xs:sequence>
<xs:element minOccurs="0" name="area_code" type="xs:string" />
<xs:element minOccurs="0" name="city" type="xs:string" />
<xs:element name="door" type="xs:int" />
<xs:element name="house" type="xs:int" />
<xs:element minOccurs="0" name="street" type="xs:string" />
</xs:sequence>
<xs:attribute name="id" type="xs:string" />
</xs:complexType>
<xs:complexType name="telephoneNumber">
<xs:sequence>
<xs:element minOccurs="0" name="area_code" type="xs:string" />
<xs:element minOccurs="0" name="country_code" type="xs:string" />
<xs:element minOccurs="0" name="id" type="xs:string" />
<xs:element minOccurs="0" name="number" type="xs:string" />
</xs:sequence>
</xs:complexType>
<xs:complexType name="check_porting_possibleResponse">
<xs:sequence>
<xs:element name="return" type="xs:boolean" />
</xs:sequence>
</xs:complexType>
<xs:complexType name="check_porting_status">
<xs:sequence>
<xs:element minOccurs="0" name="customer" type="tns:customer" />
</xs:sequence>
</xs:complexType>
<xs:complexType name="check_porting_statusResponse">
<xs:sequence>
<xs:element name="return" type="xs:boolean" />
</xs:sequence>
</xs:complexType>
<xs:complexType name="get_porting_result">
<xs:sequence>
<xs:element minOccurs="0" name="customer" type="tns:customer" />
</xs:sequence>
</xs:complexType>
<xs:complexType name="get_porting_resultResponse">
<xs:sequence>
<xs:element minOccurs="0" name="return" type="tns:portingResult" />
</xs:sequence>
</xs:complexType>
<xs:complexType name="portingResult">
<xs:sequence>
<xs:element minOccurs="0" name="comment" type="xs:string" />
<xs:element name="new_provider" type="xs:long" />
<xs:element name="success" type="xs:boolean" />
<xs:element minOccurs="0" name="customer" type="tns:customer" />
</xs:sequence>
</xs:complexType>
<xs:complexType name="schedule_batch_porting">
<xs:sequence>
<xs:element maxOccurs="unbounded" minOccurs="0" name="portingrequests" type="tns:portingRequest" />
</xs:sequence>
</xs:complexType>
<xs:complexType name="portingRequest">
<xs:sequence>
<xs:element name="new_provider" type="xs:long" />
<xs:element name="porting_date" type="xs:long" />
<xs:element minOccurs="0" name="customer" type="tns:customer" />
</xs:sequence>
</xs:complexType>
<xs:complexType name="schedule_batch_portingResponse">
<xs:sequence>
<xs:element maxOccurs="unbounded" minOccurs="0" name="return" type="xs:anyType" />
</xs:sequence>
</xs:complexType>
<xs:complexType name="statecount">
<xs:sequence />
</xs:complexType>
<xs:complexType name="statecountResponse">
<xs:sequence>
<xs:element name="return" type="xs:int" />
</xs:sequence>
</xs:complexType>
<xs:complexType name="customers">
<xs:sequence>
<xs:element maxOccurs="unbounded" minOccurs="0" name="customers" nillable="true" type="tns:customer" />
</xs:sequence>
</xs:complexType>
<xs:element name="InvalidCustomerFault" type="tns:InvalidCustomerFault" />
<xs:complexType name="InvalidCustomerFault">
<xs:sequence />
</xs:complexType>
<xs:element name="NotFinishedFault" type="tns:NotFinishedFault" />
<xs:complexType name="NotFinishedFault">
<xs:sequence />
</xs:complexType>
</xs:schema>
</wsdl:types>
<wsdl:message name="statecountResponse">
<wsdl:part element="tns:statecountResponse" name="parameters">
</wsdl:part>
</wsdl:message>
<wsdl:message name="check_porting_statusResponse">
<wsdl:part element="tns:check_porting_statusResponse" name="parameters">
</wsdl:part>
</wsdl:message>
<wsdl:message name="schedule_batch_porting">
<wsdl:part element="tns:schedule_batch_porting" name="parameters">
</wsdl:part>
</wsdl:message>
<wsdl:message name="check_porting_possible">
<wsdl:part element="tns:check_porting_possible" name="parameters">
</wsdl:part>
</wsdl:message>
<wsdl:message name="get_porting_resultResponse">
<wsdl:part element="tns:get_porting_resultResponse" name="parameters">
</wsdl:part>
</wsdl:message>
<wsdl:message name="check_porting_status">
<wsdl:part element="tns:check_porting_status" name="parameters">
</wsdl:part>
</wsdl:message>
<wsdl:message name="statecount">
<wsdl:part element="tns:statecount" name="parameters">
</wsdl:part>
</wsdl:message>
<wsdl:message name="NotFinishedFault">
<wsdl:part element="tns:NotFinishedFault" name="NotFinishedFault">
</wsdl:part>
</wsdl:message>
<wsdl:message name="get_porting_result">
<wsdl:part element="tns:get_porting_result" name="parameters">
</wsdl:part>
</wsdl:message>
<wsdl:message name="check_porting_possibleResponse">
<wsdl:part element="tns:check_porting_possibleResponse" name="parameters">
</wsdl:part>
</wsdl:message>
<wsdl:message name="InvalidCustomerFault">
<wsdl:part element="tns:InvalidCustomerFault" name="InvalidCustomerFault">
</wsdl:part>
</wsdl:message>
<wsdl:message name="schedule_batch_portingResponse">
<wsdl:part element="tns:schedule_batch_portingResponse" name="parameters">
</wsdl:part>
</wsdl:message>
<wsdl:portType name="NumberPortingService">
<wsdl:operation name="check_porting_possible">
<wsdl:input message="tns:check_porting_possible" name="check_porting_possible">
</wsdl:input>
<wsdl:output message="tns:check_porting_possibleResponse" name="check_porting_possibleResponse">
</wsdl:output>
<wsdl:fault message="tns:InvalidCustomerFault" name="InvalidCustomerFault">
</wsdl:fault>
</wsdl:operation>
<wsdl:operation name="check_porting_status">
<wsdl:input message="tns:check_porting_status" name="check_porting_status">
</wsdl:input>
<wsdl:output message="tns:check_porting_statusResponse" name="check_porting_statusResponse">
</wsdl:output>
<wsdl:fault message="tns:InvalidCustomerFault" name="InvalidCustomerFault">
</wsdl:fault>
</wsdl:operation>
<wsdl:operation name="get_porting_result">
<wsdl:input message="tns:get_porting_result" name="get_porting_result">
</wsdl:input>
<wsdl:output message="tns:get_porting_resultResponse" name="get_porting_resultResponse">
</wsdl:output>
<wsdl:fault message="tns:NotFinishedFault" name="NotFinishedFault">
</wsdl:fault>
<wsdl:fault message="tns:InvalidCustomerFault" name="InvalidCustomerFault">
</wsdl:fault>
</wsdl:operation>
<wsdl:operation name="schedule_batch_porting">
<wsdl:input message="tns:schedule_batch_porting" name="schedule_batch_porting">
</wsdl:input>
<wsdl:output message="tns:schedule_batch_portingResponse" name="schedule_batch_portingResponse">
</wsdl:output>
<wsdl:fault message="tns:InvalidCustomerFault" name="InvalidCustomerFault">
</wsdl:fault>
</wsdl:operation>
<wsdl:operation name="statecount">
<wsdl:input message="tns:statecount" name="statecount">
</wsdl:input>
<wsdl:output message="tns:statecountResponse" name="statecountResponse">
</wsdl:output>
</wsdl:operation>
</wsdl:portType>
<wsdl:binding name="NumberPortingServiceServiceSoapBinding" type="tns:NumberPortingService">
<soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http" />
<wsdl:operation name="check_porting_possible">
<soap:operation soapAction="" style="document" />
<wsdl:input name="check_porting_possible">
<soap:body use="literal" />
</wsdl:input>
<wsdl:output name="check_porting_possibleResponse">
<soap:body use="literal" />
</wsdl:output>
<wsdl:fault name="InvalidCustomerFault">
<soap:fault name="InvalidCustomerFault" use="literal" />
</wsdl:fault>
</wsdl:operation>
<wsdl:operation name="check_porting_status">
<soap:operation soapAction="" style="document" />
<wsdl:input name="check_porting_status">
<soap:body use="literal" />
</wsdl:input>
<wsdl:output name="check_porting_statusResponse">
<soap:body use="literal" />
</wsdl:output>
<wsdl:fault name="InvalidCustomerFault">
<soap:fault name="InvalidCustomerFault" use="literal" />
</wsdl:fault>
</wsdl:operation>
<wsdl:operation name="get_porting_result">
<soap:operation soapAction="" style="document" />
<wsdl:input name="get_porting_result">
<soap:body use="literal" />
</wsdl:input>
<wsdl:output name="get_porting_resultResponse">
<soap:body use="literal" />
</wsdl:output>
<wsdl:fault name="NotFinishedFault">
<soap:fault name="NotFinishedFault" use="literal" />
</wsdl:fault>
<wsdl:fault name="InvalidCustomerFault">
<soap:fault name="InvalidCustomerFault" use="literal" />
</wsdl:fault>
</wsdl:operation>
<wsdl:operation name="schedule_batch_porting">
<soap:operation soapAction="" style="document" />
<wsdl:input name="schedule_batch_porting">
<soap:body use="literal" />
</wsdl:input>
<wsdl:output name="schedule_batch_portingResponse">
<soap:body use="literal" />
</wsdl:output>
<wsdl:fault name="InvalidCustomerFault">
<soap:fault name="InvalidCustomerFault" use="literal" />
</wsdl:fault>
</wsdl:operation>
<wsdl:operation name="statecount">
<soap:operation soapAction="" style="document" />
<wsdl:input name="statecount">
<soap:body use="literal" />
</wsdl:input>
<wsdl:output name="statecountResponse">
<soap:body use="literal" />
</wsdl:output>
</wsdl:operation>
</wsdl:binding>
<wsdl:service name="NumberPortingServiceService">
<wsdl:port binding="tns:NumberPortingServiceServiceSoapBinding" name="NumberPortingServicePort">
<soap:address location="http://localhost:8083/numberportingservice" />
</wsdl:port>
</wsdl:service>
</wsdl:definitions>
Have anybody an idea why I got this failure I mentioned above when trying to start the BPEL process?
Please help me :)
Thanks a lot!!!
Steve

Or can you invoke the service from the 'gui' of the deployed webservice in the glassfish as ?
you need to check if either the service doesnt work or the invoke of the service from bpel is the problem

Similar Messages

Invoking webservice through bpel process

Hi, I created a webservice for a java code. I created a simple bpel process to invoke the webservice. Its throwing below error when running the bpel process. I tested the webservice alone. it works fine. Any help is highly apreciated.
Thanks, Ram....
when invoking locally the endpoint 'http://wtus081806-6:9700/Hrinfo-java_test_1-context-root/default', ; nested exception is: ORABPEL-05210 No BPEL archive files. The process domain cannot locate any BPEL archives for process "unknown". If you have deployed a process please check that it is located in the directory "C:\OraHome_1\integration\orabpel\domains\default\deploy".</summary>
</part>
<part name="detail">
<detail>ORABPEL-05210 No BPEL archive files. The process domain cannot locate any BPEL archives for process "unknown". If you have deployed a process please check that it is located in the directory "C:\OraHome_1\integration\orabpel\domains\default\deploy".</detail>
</part>

I remember this being a bug in 10.1.2.0.2 - as somehow the servlet thinks the call would be for the bpel engine, instead of the webservice endpoint,
so I recommend 2 things .. don/t name the operation default
'http://wtus081806-6:9700/Hrinfo-java_test_1-context-root/default'
and if this does not help, try to set optSOAPShortcut -> false on the BPEL Domain ..

JDeveloper 11g with BPEL process Manager 10.1.3.1.0

Hi,
Here is my requirement.
To develop a simple web application which talks to a Business work flow developed using BPEL.
The Setup I wanted to work on
JDeveloper 11g.
BPEL process Manager 10.1.3.1.0.
Now the problems seems to be is that JDeveloper 11g doesnt seem to be having BPEL Designer ,is there is plugin for me to get BPEL Designer in my JDeveloper 11g.
Could some body tell me if i can use JDeveloper 10.1.3.1.0 with BPEL process Manager 10.1.3.1.0 if yes then
how do we configure the JDeveloper 10.1.3.1.0 to point to BPEL process Manager 10.1.3.1.0.
Regards
Harish

Huh? In the subject you're talking about BPEL 10.1.3.x and now you're asking for 10.1.2?
Anyway, you need the corresponding JDeveloper version to develop the BPEL workflow, ie JDev 10.1.3.4 for BPEL 10.1.3.4 or JDev 10.1.2. for BPEL 10.1.2.
You can install as much as possible JDeveloper versions on your machine. As long as they are installed in a different home. I usually have three to six installations.
Develop your workflow in the JDev matching the BPEL version and develop your UI in JDev 11g calling the BPEL as a WebService.
--olaf

OSB -- Invoking an asynchronous BPEL process in Oracle Service Bus

Hi All,
Can any one let me know how to invoke the Asynchronous BPEL process in OSB.
Thanks in Advance,
Feroz Tasha.

Hey,
What i was trying to say was that when you export your OSB project to file system, you can edit the business service in a file editor(e.g notepad, editplus etc).
In that, instead of suppose 127.0.0.1 u can put a token say @@HOST_NAME@@ and for a port say 7001 as @@PORT_NUMBER@@.
Then an ant script can replace the values of above 2 tokens with apt values, create a jar out of it and deploy it on the server.
There are numerous ANT scripts and examples available online.
Hope this helps.

I tried to invoke WS from BPEL process

I tried to invoke WS from BPEL process. And error occurred when I deployed the process.
Error:
[ERROR ORABPEL-10902]: COMPILING FAILED.
[NOTE]: IN "bpel.xml", XML syntax analysis failed. The reason is "Part Element not defined".
In "http://192.168.0.188:8989/newTest-newTest-context-root/MyorderListWS?wsdl" , Message Part Element "{http://www.w3.org/2001/XMLSchema}any" is not defined in any SCHEMA。
Please make sure to spell the definite name of the ELEMENT correctly and import WSDL completely.
wsdl file(IMyorderListWS.wsdl)
<?xml version = '1.0' encoding = 'UTF-8'?>


<definitions
name="MyorderListWS"
targetNamespace="http://zbht/com/orderList.wsdl"
xmlns="http://schemas.xmlsoap.org/wsdl/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
xmlns:tns="http://zbht/com/orderList.wsdl"
xmlns:ns1="http://zbht.com/IMyorderListWS.xsd">
<types>
<schema
targetNamespace="http://zbht.com/IMyorderListWS.xsd"
xmlns="http://www.w3.org/2001/XMLSchema"
xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/"/>
</types>
<message name="getResInfo0Request">
<part name="custID" type="xsd:string"/>
<part name="prodctID" type="xsd:string"/>
</message>
<message name="getResInfo0Response">
<part name="return" element="xsd:any"/>
</message>
<portType name="orderListPortType">
<operation name="getResInfo">
<input name="getResInfo0Request" message="tns:getResInfo0Request"/>
<output name="getResInfo0Response" message="tns:getResInfo0Response"/>
</operation>
</portType>
<binding name="orderListBinding" type="tns:orderListPortType">
<soap:binding style="rpc" transport="http://schemas.xmlsoap.org/soap/http"/>
<operation name="getResInfo">
<soap:operation soapAction="" style="rpc"/>
<input name="getResInfo0Request">
<soap:body use="encoded" namespace="MyorderListWS" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"/>
</input>
<output name="getResInfo0Response">
<soap:body use="literal" namespace="MyorderListWS"/>
</output>
</operation>
</binding>
<service name="MyorderListWS">
<port name="orderListPort" binding="tns:orderListBinding">
<soap:address location="http://192.168.0.188:8989/newTest-newTest-context-root/MyorderListWS"/>
</port>
</service>
</definitions>
/*****************************************************************************************/

In your wsdl ...
instead of
<part name="custID" type="xsd:string"/>
try
<part name="custID" element="xsd:string"/>
the part is usually an element such as
<element name="BPELProcess1ProcessResponse">
<complexType>
<sequence>
<element name="result" type="string"/>
</sequence>
</complexType>
</element>
hth clemens

How to invoke EJB with BPEL?

How to invoke EJB with BPEL?
I know there are two ways: WSIF and SOAP.
But I don't how to do step by step. Please help me.
Thanks
Melody

And I used the method said by soaUser to generate the WSIF binding WSDL file for a Java class.
Then I put this WSDL file into a BPEL project directory and create a partner link with this.
But after I invoke this BPEL, a error happen:
Error while determining signature of method sayHello : The meta information is not consistent.; nested exception is:
org.collaxa.thirdparty.apache.wsif.WSIFException: Could not instantiate class 'javaws.SayHelloElement'; nested exception is:
java.lang.ClassNotFoundException: javaws.SayHelloElement
Even after I put the Java class into the %SOA_HOME%\bpel\system\classes directory, this error still happen.
How to resolve?
Thanks,
Melody

Can we invoke webservice with multiple parts in wsdl?

Can we invoke webservice with multiple parts in wsdl?
Thanks

Yes we can invoke a web service with multiple parts for the input message.
You just have to assign to the relevant parts of the partner link input variable before invoking.
Regards,
Shanmu.

Can't invoke WS from BPEL process: Unable to locate activated endpoint

I have a simple Calculator Web Service deployed on Glassfish, that I can access with any kind of SOAP client (e.g. soapUI). I have then created a BPEL process that invokes this external Web Service (which happens to run on the same Glassfish server, but that's largely irrelevant I suppose). I can instantiate and invoke the BPEL process (I've tried it with a dummy assign earlier just to make sure, and it runs successfully), but the BPEL process doesn't seem to be able to locate the external Web Service. I get the following fault:
<S:Envelope xmlns:S="http://schemas.xmlsoap.org/soap/envelope/">
<S:Body>
<ns2:Fault xmlns:ns2="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ns3="http://www.w3.org/2003/05/soap-envelope">
<faultcode>ns2:Server</faultcode>
<faultstring>javax.jbi.messaging.MessagingException: Unable to locate activated endpoint for service connection {SigningCompositeApp}CalculatorService SignedCalculatorService.</faultstring>
<detail>
<ns2:exception class="java.lang.RuntimeException" note="To disable this feature, set com.sun.xml.ws.fault.SOAPFaultBuilder.disableCaptureStackTrace system property to false" xmlns:ns2="http://jax-ws.dev.java.net/">
<message>javax.jbi.messaging.MessagingException: Unable to locate activated endpoint for service connection {SigningCompositeApp}CalculatorService SignedCalculatorService.</message>
<ns2:stackTrace>
<ns2:frame class="com.sun.xml.ws.server.provider.AsyncProviderInvokerTube$AsyncProviderCallbackImpl" file="AsyncProviderInvokerTube.java" line="114" method="sendError"/>
<ns2:frame class="com.sun.jbi.httpsoapbc.jaxwssupport.AsyncJBIProvider" file="AsyncJBIProvider.java" line="136" method="invoke"/>
<ns2:frame class="com.sun.jbi.httpsoapbc.jaxwssupport.AsyncJBIProvider" file="AsyncJBIProvider.java" line="94" method="invoke"/>
<ns2:frame class="sun.reflect.GeneratedMethodAccessor305" line="unknown" method="invoke"/>
<ns2:frame class="sun.reflect.DelegatingMethodAccessorImpl" file="DelegatingMethodAccessorImpl.java" line="25" method="invoke"/>
<ns2:frame class="java.lang.reflect.Method" file="Method.java" line="597" method="invoke"/>
<ns2:frame class="com.sun.jbi.httpsoapbc.jaxwssupport.InvokerImpl" file="InvokerImpl.java" line="72" method="invoke"/>
<ns2:frame class="com.sun.xml.ws.api.server.Invoker" file="Invoker.java" line="115" method="invokeAsyncProvider"/>
<ns2:frame class="com.sun.xml.ws.server.InvokerTube$2" file="InvokerTube.java" line="166" method="invokeAsyncProvider"/>
<ns2:frame class="com.sun.xml.ws.server.provider.AsyncProviderInvokerTube" file="AsyncProviderInvokerTube.java" line="80" method="processRequest"/>
<ns2:frame class="com.sun.xml.ws.api.pipe.Fiber" file="Fiber.java" line="595" method="__doRun"/>
<ns2:frame class="com.sun.xml.ws.api.pipe.Fiber" file="Fiber.java" line="554" method="_doRun"/>
<ns2:frame class="com.sun.xml.ws.api.pipe.Fiber" file="Fiber.java" line="539" method="doRun"/>
<ns2:frame class="com.sun.xml.ws.api.pipe.Fiber" file="Fiber.java" line="388" method="run"/>
<ns2:frame class="java.util.concurrent.ThreadPoolExecutor$Worker" file="ThreadPoolExecutor.java" line="885" method="runTask"/>
<ns2:frame class="java.util.concurrent.ThreadPoolExecutor$Worker" file="ThreadPoolExecutor.java" line="907" method="run"/>
<ns2:frame class="java.lang.Thread" file="Thread.java" line="619" method="run"/>
</ns2:stackTrace>
<ns2:cause class="javax.jbi.messaging.MessagingException" note="To disable this feature, set com.sun.xml.ws.fault.SOAPFaultBuilder.disableCaptureStackTrace system property to false">
<message>Unable to locate activated endpoint for service connection {SigningCompositeApp}CalculatorService SignedCalculatorService.</message>
<ns2:stackTrace>
<ns2:frame class="com.sun.jbi.messaging.MessageService" file="MessageService.java" line="492" method="addressExchange"/>
<ns2:frame class="com.sun.jbi.messaging.MessageService" file="MessageService.java" line="326" method="doExchange"/>
<ns2:frame class="com.sun.jbi.messaging.DeliveryChannelImpl" file="DeliveryChannelImpl.java" line="209" method="send"/>
<ns2:frame class="com.sun.jbi.httpsoapbc.InboundMessageProcessor" file="InboundMessageProcessor.java" line="268" method="sendInOut"/>
<ns2:frame class="com.sun.jbi.httpsoapbc.InboundMessageProcessor" file="InboundMessageProcessor.java" line="479" method="executeSOAP"/>
<ns2:frame class="com.sun.jbi.httpsoapbc.InboundMessageProcessor" file="InboundMessageProcessor.java" line="215" method="execute"/>
<ns2:frame class="com.sun.jbi.httpsoapbc.jaxwssupport.AsyncJBIProvider" file="AsyncJBIProvider.java" line="134" method="invoke"/>
<ns2:frame class="com.sun.jbi.httpsoapbc.jaxwssupport.AsyncJBIProvider" file="AsyncJBIProvider.java" line="94" method="invoke"/>
<ns2:frame class="sun.reflect.GeneratedMethodAccessor305" line="unknown" method="invoke"/>
<ns2:frame class="sun.reflect.DelegatingMethodAccessorImpl" file="DelegatingMethodAccessorImpl.java" line="25" method="invoke"/>
<ns2:frame class="java.lang.reflect.Method" file="Method.java" line="597" method="invoke"/>
<ns2:frame class="com.sun.jbi.httpsoapbc.jaxwssupport.InvokerImpl" file="InvokerImpl.java" line="72" method="invoke"/>
<ns2:frame class="com.sun.xml.ws.api.server.Invoker" file="Invoker.java" line="115" method="invokeAsyncProvider"/>
<ns2:frame class="com.sun.xml.ws.server.InvokerTube$2" file="InvokerTube.java" line="166" method="invokeAsyncProvider"/>
<ns2:frame class="com.sun.xml.ws.server.provider.AsyncProviderInvokerTube" file="AsyncProviderInvokerTube.java" line="80" method="processRequest"/>
<ns2:frame class="com.sun.xml.ws.api.pipe.Fiber" file="Fiber.java" line="595" method="__doRun"/>
<ns2:frame class="com.sun.xml.ws.api.pipe.Fiber" file="Fiber.java" line="554" method="_doRun"/>
<ns2:frame class="com.sun.xml.ws.api.pipe.Fiber" file="Fiber.java" line="539" method="doRun"/>
<ns2:frame class="com.sun.xml.ws.api.pipe.Fiber" file="Fiber.java" line="388" method="run"/>
<ns2:frame class="java.util.concurrent.ThreadPoolExecutor$Worker" file="ThreadPoolExecutor.java" line="885" method="runTask"/>
<ns2:frame class="java.util.concurrent.ThreadPoolExecutor$Worker" file="ThreadPoolExecutor.java" line="907" method="run"/>
<ns2:frame class="java.lang.Thread" file="Thread.java" line="619" method="run"/>
</ns2:stackTrace>
</ns2:cause>
</ns2:exception>
</detail>
</ns2:Fault>
</S:Body>
</S:Envelope>
For good measure, here's the WSDL (and partner link defn) for the external WS:
<?xml version="1.0" encoding="UTF-8"?>
<definitions name="CalculatorWSExternal" targetNamespace="http://j2ee.netbeans.org/wsdl/CalculatorWSExternal"
xmlns="http://schemas.xmlsoap.org/wsdl/"
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:tns="http://j2ee.netbeans.org/wsdl/CalculatorWSExternal" xmlns:ns="http://calculator.me.org/" xmlns:plnk="http://docs.oasis-open.org/wsbpel/2.0/plnktype" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/">
<types>
<xsd:schema targetNamespace="http://j2ee.netbeans.org/wsdl/CalculatorWSExternal">
<xsd:import namespace="http://calculator.me.org/" schemaLocation="CalculatorWSService.xsd"/>
</xsd:schema>
</types>
<message name="addRequest">
<part name="add" element="ns:add"/>
</message>
<message name="addReply">
<part name="addResponse" element="ns:addResponse"/>
</message>
<portType name="CalculatorWSExternalPortType">
<operation name="add">
<input name="input1" message="tns:addRequest"/>
<output name="output1" message="tns:addReply"/>
</operation>
</portType>
<binding name="CalculatorWSExternalBinding" type="tns:CalculatorWSExternalPortType">
<soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
<operation name="add">
<soap:operation/>
<input name="input1">
<soap:body use="literal"/>
</input>
<output name="output1">
<soap:body use="literal"/>
</output>
</operation>
</binding>
<service name="CalculatorWSExternalService">
<port name="CalculatorWSExternalPort" binding="tns:CalculatorWSExternalBinding">
<soap:address location="http://localhost:8080/CalculatorApp/CalculatorWSService"/>
</port>
</service>
<plnk:partnerLinkType name="CalculatorWSExternal1">

<plnk:role name="CalculatorWSExternalPortTypeRole" portType="tns:CalculatorWSExternalPortType"/>
</plnk:partnerLinkType>
</definitions>
Any help? I've seen someone post a similar problem on the forum at http://forum.java.sun.com/thread.jspa?threadID=5273187&messageID=10157363#10157363
but I haven't seen any answers. Thanks!
Edited by: tboubez on Jun 9, 2008 10:56 AM

Check the ports of Web services and those of BPEL, as Hambo have different communication ports.
Normally Webservices point to the port 8080 and BPEL to 18181 or 9084.
Check and I accounts.
Greetings.

Problem invoking from a BPEL process webservice client

I have a BPEL Synchronous process that invokes a webservice deployed on Tomcat. The process executes without any exception when I run it from the BPEL Console. Since I want to execute the BPEL process as a command line operation, I created a BPEL Process Webservice client from scratch using Axis as described in Tutorial7 - InvokingBPELProcesses.pdf. However when I try to execute the client, I get the following error:
AxisFault
faultCode: {http://xml.apache.org/axis/}Server.generalException
faultSubcode:
faultString: Dispatcher send error.
An error occurred while sending a batch message to the dispatch queue. The exception is: Failed to create "java:comp/env/ejb/local/DispatcherLocalBean" bean; exception reported is: "javax.naming.NameNotFoundException: ejb/local/DispatcherLocalBean not found in startup_war
     at com.oracle.naming.J2EEContext.getSubContext(J2EEContext.java:93)
     at com.oracle.naming.J2EEContext.lookup(J2EEContext.java:76)
     at com.evermind.server.ApplicationContext.lookup(ApplicationContext.java:177)
     at com.evermind.server.ApplicationContext.lookup(ApplicationContext.java:119)
     at javax.naming.InitialContext.lookup(InitialContext.java:347)
     at com.collaxa.cube.engine.util.CubeEngineBeanRegistry.lookupDispatcherLocalBean(CubeEngineBeanRegistry.java:165)
     at com.collaxa.cube.engine.util.CubeEngineBeanCache.getDispatcherLocalBean(CubeEngineBeanCache.java:91)
     at com.collaxa.cube.engine.dispatch.DispatchHelper.sendLocal(DispatchHelper.java:229)
     at com.collaxa.cube.engine.dispatch.Dispatcher.receive(Dispatcher.java:430)
     at com.collaxa.cube.engine.dispatch.Dispatcher.receive(Dispatcher.java:357)
     at com.collaxa.cube.engine.dispatch.Dispatcher.update(Dispatcher.java:253)
     at com.collaxa.cube.engine.core.event.DomainObserverRegistry.notify(DomainObserverRegistry.java:124)
     at com.collaxa.cube.engine.core.event.DomainObserverRegistry.notify(DomainObserverRegistry.java:66)
     at com.collaxa.cube.engine.deployment.CubeProcessHolder.notify(CubeProcessHolder.java:727)
     at com.collaxa.cube.engine.deployment.CubeProcessHolder.addProcess(CubeProcessHolder.java:697)
     at com.collaxa.cube.engine.deployment.CubeProcessHolder.bind(CubeProcessHolder.java:632)
     at com.collaxa.cube.engine.deployment.CubeProcessHolder.loadAndBind(CubeProcessHolder.java:605)
     at com.collaxa.cube.engine.deployment.CubeProcessHolder.loadAndBind(CubeProcessHolder.java:592)
     at com.collaxa.cube.engine.deployment.CubeProcessHolder.getProcess(CubeProcessHolder.java:494)
     at com.collaxa.cube.engine.deployment.CubeProcessHolder.getProcess(CubeProcessHolder.java:429)
     at com.collaxa.cube.engine.CubeEngine.lookupProcess(CubeEngine.java:840)
     at com.collaxa.cube.ws.wsdl.WSDLManager.getProcess(WSDLManager.java:437)
     at com.collaxa.cube.ws.wsdl.WSDLManager.getPartnerWSDL(WSDLManager.java:300)
     at com.collaxa.cube.ws.soap.providers.CXSOAPProvider.processBPELMessage(CXSOAPProvider.java:175)
     at com.collaxa.cube.ws.soap.providers.CXSOAPProvider.invoke(CXSOAPProvider.java:111)
     at org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrategy.java:71)
     at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:156)
     at org.apache.axis.SimpleChain.invoke(SimpleChain.java:126)
     at org.apache.axis.handlers.soap.SOAPService.invoke(SOAPService.java:437)
     at org.apache.axis.server.AxisServer.invoke(AxisServer.java:316)
     at org.apache.axis.transport.http.AxisServlet.doPost(AxisServlet.java:701)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
     at org.apache.axis.transport.http.AxisServletBase.service(AxisServletBase.java:335)
     at com.collaxa.cube.fe.CollaxaServlet.service(CollaxaServlet.java:117)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:765)
     at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:317)
     at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:790)
     at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:270)
     at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:112)
     at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:186)
     at java.lang.Thread.run(Thread.java:534)
".
Can someone please tell me what is it I am doing wrong?

I was using
Oracle BPEL Server version 2.0
Build: 2004.06.17.14.40
Build time: Thu Jun 17 14:40:58 PDT 2004
However, I downloaded the latest version of the Process Manager and did not face the same problem.

Unable to access endpoint while invoking webservice in bpel

I am getting an error "Unable to access the following endpoint(s):http://xxxxxxxxxxxxxxxxxxx/example.svc" while referencing the external webservice in bpel.
The webservice is created on a microsoft dynamics ax platform and it is hosted on iis 7.0. Both servers are in the same domain.
I am using soa suite 11.1.1.5 and Jdeveloper 11.1.1.5.
Any help will be really appreciated.
Thanks,
Anshul

Neeraj,
- Are you able to access the endpoint through browser?
me: yes
- Is the network connectivity (firewall, port access) from SOA server to IIS available?
me: yes
- Are you able to access the service while creating the reference in Jdeveloper?
me: yes
- If the target service is 2-way SSL enabled, are the required certificates imported in client keystore?
me: The service is not ssl enabled it is just using windows authentication.
"Both servers are in the same domain" it means that as the service is windows enabled so it will authenticated only for the domain user.(correct me if i am wrong).
Regards,
Anshul

Need help !!! Regarding invoking Webservices with Basic Auth

I have a partner who requires me to pass credentials in order to invoke their Webservice.
I have created a Partner link using a local WSDL (copy of the original partner's WSDL) and assigned the following properties
<property name="HTTPbasicHeaders">credentials</property>
<property name="basicUsername">hilal.khan</property>
<property name="basicPassword">welcome123</property>
And invoked this partnerlink in a Synchronous BPEL process, the invocation fails with the following error message
<remoteFault xmlns="http://schemas.oracle.com/bpel/extension"><part name="summary"><summary>exception on JaxRpc invoke: HTTP transport error: javax.xml.soap.SOAPException: java.security.PrivilegedActionException: javax.xml.soap.SOAPException: Bad response: 401 Unauthorized</summary>
</part></remoteFault>
Looks like I am missing the way in which these credentials should be sent, I know for sure that the values being sent are correct - I tried to open the WSDL from a browser and it prompted me with a username/password window and I entered the same credentials and it then took me to the WSDL. Can one of you please help me figure out the issue and resolve it.

Hi,
In BPEL.xml file that is built for bpel pass the binding with the httpUsername and httpPassword which you can make anything.
<partnerLinkBinding name="PartnerLink_SPTel_Register">
<property name="wsdlLocation">RegisterServiceRef.wsdl</property>
<property name="httpUsername">dummy</property>
<property name="httpPassword">dummy</property>
</partnerLinkBinding>
and in the BPEL process change the value of httpUsername and httpPassword dynamically to whatever you want.
<copy>
<from variable="httpUsername"/>
<to partnerLink="EventService_Partner" bpelx:property="httpUsername"/>
</copy>
<copy>
<from variable="httpPassword"/>
<to partnerLink="EventService_Partner" bpelx:property="httpPassword"/>
</copy>
This works great if you have to pass different credentials to the same WS depending on who accesses the bpel process.
hope this helps
Sandeep

Getting error connection timed out while invoking webservice from bpel.

Hi,
I am trying to call a secure webservice developed in .Net having extension .svc from the bpel service and in response i am getting error
com.oracle.bpel.client.BPELFault: faultName: {{http://schemas.oracle.com/bpel/extension}remoteFault}
messageType: {{http://schemas.oracle.com/bpel/extension}RuntimeFaultMessage}
parts: {{summary=<summary>exception on JaxRpc invoke: HTTP transport error: javax.xml.soap.SOAPException: java.security.PrivilegedActionException: javax.xml.soap.SOAPException: Message send failed: Connection timed out: connect</summary>
I am able to call this web service from the java programme using HTTPClient by setting the username/password and soapaction in http Header but not from the BPEL process. This .Net service is synchronous in nature. I also set the proxy in opmn.xml but didn't got any success.
Please reply me ASAP. Need urgent help.
Thanks.

Are you working on 11g ? if this is 11g
How are you invoking the webservice ...does it have any authentication..
If the webservice which you are invoking has basic http authentication...
1. In the composite.xml file, right click on the reference and configure WS policies. In security tab, add a security policy named"oracle/wss_http_token_client_policy"
2. Add two binding properties for the reference
(i) oracle.webservices.auth.username
(ii) oracle.webservices.auth.password
and provide the username and password for those two properties...
Just try this out...
Thanks,
N

Oracle DB Adapter throwing NLS_LANGUAGE' by invoking SP in BPEL Process

Hi,
While i am invoking a Store procedure, the DB Adapter in BPEL process reslting throwing following below error in
<fault>
<bpelFault>
<faultType>0</faultType>
<bindingFault>
<part name="summary">
<summary>Exception occured when binding was invoked. Exception occured during invocation of JCA binding: "JCA Binding execute of Reference operation 'ESOAAdd_DBWraper' failed due to: Stored procedure invocation error. Error while trying to prepare and execute the BPEL_ESOAADD_DBWRAPER.XXEMC_INT_PKG$AR_TRX_PRC API. An error occurred while preparing and executing the BPEL_ESOAADD_DBWRAPER.XXEMC_INT_PKG$AR_TRX_PRC API. Cause: java.sql.SQLException: ORA-20001: Oracle error -20001: ORA-20001: Oracle error -2074: ORA-02074: cannot SET NLS in a distributed transaction has been detected in fnd_global.set_nls.set_parameter('NLS_LANGUAGE','AMERICAN'). has been detected in fnd_global.set_nls. ORA-06512: at "APPS.APP_EXCEPTION", line 72 ORA-06512: at "APPS.FND_GLOBAL", line 245 ORA-06512: at "APPS.FND_GLOBAL", line 1426 ORA-06512: at "APPS.FND_GLOBAL", line 1684 ORA-06512: at "APPS.FND_GLOBAL", line 2309 ORA-06512: at "APPS.FND_GLOBAL", line 2447 ORA-06512: at "APPS.FND_GLOBAL", line 2385 ORA-06512: at "APPS.XXEMC_INT_PKG", line 22 ORA-06512: at "APPS.BPEL_ESOAADD_DBWRAPER", line 620 ORA-06512: at line 1 Check to ensure that the API is defined in the database and that the parameters match the signature of the API. This exception is considered not retriable, likely due to a modelling mistake. To classify it as retriable instead add property nonRetriableErrorCodes with value "-20001" to your deployment descriptor (i.e. weblogic-ra.xml). To auto retry a retriable fault set these composite.xml properties for this invoke: jca.retry.interval, jca.retry.count, and jca.retry.backoff. All properties are integers. ". The invoked JCA adapter raised a resource exception. Please examine the above error message carefully to determine a resolution. </summary>
</part>
<part name="detail">
<detail>ORA-20001: Oracle error -20001: ORA-20001: Oracle error -2074: ORA-02074: cannot SET NLS in a distributed transaction has been detected in fnd_global.set_nls.set_parameter('NLS_LANGUAGE','AMERICAN'). has been detected in fnd_global.set_nls. ORA-06512: at "APPS.APP_EXCEPTION", line 72 ORA-06512: at "APPS.FND_GLOBAL", line 245 ORA-06512: at "APPS.FND_GLOBAL", line 1426 ORA-06512: at "APPS.FND_GLOBAL", line 1684 ORA-06512: at "APPS.FND_GLOBAL", line 2309 ORA-06512: at "APPS.FND_GLOBAL", line 2447 ORA-06512: at "APPS.FND_GLOBAL", line 2385 ORA-06512: at "APPS.XXEMC_INT_PKG", line 22 ORA-06512: at "APPS.BPEL_ESOAADD_DBWRAPER", line 620 ORA-06512: at line 1 </detail>
</part>
<part name="code">
<code>20001</code>
</part>
</bindingFault>
</bpelFault>
</fault>
Can any one gude me to over come from this error.
Thanks,
Srikanth

I believe you are invoking a Standard Seeded API in Oracle EBS. Please use the Oracle Apps Adapter instead of the Database Adapter.
Also, before the API call, make sure you invoke the SET_CLIENT_INFO procedure under the package DBMS_APPLICATION_INFO. While invoking this set client info procedure, you need to pass an input of 0 (zero) . Confirm the same with your EBS Experts in the team.
Also, now when calling the Standard API, you need to pass the credentials in the invoke activity header properties.
look at this link for my suggestions on the same
Re: Error while Uploading PO's into Oracle
Let me know...
Hope this helps,
N

Error while invoking an asynchronous BPEL process

Hi ,
I am trying to call an asynchronous BPEL process through java client.
Following is the code which I got from SOA bpel samples present in the following location
<SOA_HOME>\bpel\samples\tutorials\102.InvokingProcesses\rmi\com\otn\samples\async
The code fails while registering the callback
String convId = GUIDGenerator.generateGUID();
nm.setProperty(NormalizedMessage.CONVERSATION_ID, convId);
deliveryService.post("HelloWorld", "initiate", nm);
// register the callback
watchdog.registerAsyncCallback(convId, testAsyncHandler,
locator.getDomainAuth());
The error says java.lang.NoClassDefFoundError: org/collaxa/thirdparty/json/JSONString
I tried to search for this in google. But it seems noone has got this error or maybe noone has used this at all.
Maybe I am missing some jar file, but I am unable locate that.
Can someone help me in this please.

Hi,
These sort of class not found errors come when you are running from a client which does not have all the jar files requried to invoke BPEL using the client API.
org/collaxa/thirdparty/json/JSONString is orabpel-thirdparty.jar.
The complete list of Jar files you would need in the classpath are:
ejb.jar ($ORACLE_HOME/home/lib)
oc4j-internal.jar ($ORACLE_HOME/home/lib)
optic.jar ($ORACLE_HOME/opmn/lib)
orabpel-common.jar ($ORACLE_HOME/bpel/lib)
orabpel-thirdparty.jar ($ORACLE_HOME/bpel/lib)
orabpel.jar ($ORACLE_HOME/bpel/lib)
Hope this helps,
Regards,
Shanmu.
http://www.prshanmu.com/articles/

OWSM problems while associating clientAgent with BPEL process

Hi All,
Refering to the PDF *"Securing Oracle SOA Applications by Using Oracle Web Services Manager (Oracle WSM) Agents.pdf"* we made an clientAgent and associated that with a simple BPEL process. After that we did the following:
1) Change the Configuration Directory (with the component id of the clientAgent)
2) Enable Web Services Agent (which was not mentioned in the pdf).
3) Restart the SOA server.
At the time of executing the BPEL process it is giving an error like "internal server error". Log is not being generated for clientAgent. At BPEL domaim log it is giving the following error:
ORABPEL-02152
Instance not found in datasource.
The process domain was unable to fetch the instance with key "0ec681d22ef098ba:-529c35a1:1220cecf7e4:-7fcf" from the datasource.
Please check that the instance key "0ec681d22ef098ba:-529c35a1:1220cecf7e4:-7fcf" refers to a valid instance that has been started and not removed from the process domain.
Please reslove as early as possible.
Thanks in Advance.
Chandra.

There are a few things you can do when trying to troubleshoot this kind of problem:
1) tunnel the interaction between the BPEL server and the web service to see what SOAP messages are exchanged.
2) try to turn debugging of the ws layer on: BPEL Console>Manage Domain>Logging
2) email us your project, including the WSDL of your service so that we can take a look at it.
Finally, one best practice is to never think in terms of Java object. Instead always start by designing your WSDLs and XSDs thinking of ports and XML documents and then generate the stubs. This will guaranty that your service is interoperable.
Edwin

Unable to invoke Webservice with BPEL process

Similar Messages

Maybe you are looking for