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.

Similar Messages

Invoking ODI Scenario from a BPEL process - Resolved

I new to Oracle products.
I am exploring Oracle Data Integrator tool.
I would like to call ODI scenario from a BPEL process.
I created a scenario in ODI, I have SOA suite10.1.3.3 installed in my machine.
In some portal I have read that, we need to deploy apache axis to Oracle App server and then deploy the ODI public web service to axis. This public web service facilitates us to call scenario from partner link.
Following are my questions:
1) I guess Oracle App server acts as webservice container too. Why should I use apache axis here?
2)If axis must be used, please let me know how to deploy it to OAS.
If axis is not required, please guide me how to deploy public web service to OAS.
Thanks!!

Hi:
I have similar problem, when invoke ODI Scenario from a BPEL Process, the error in ODI Designer is:
java.lang.NullPointerException
     at com.sunopsis.dwg.dbobj.SnpSession.a(SnpSession.java)
     at com.sunopsis.dwg.dbobj.SnpSession.y(SnpSession.java)
     at com.sunopsis.dwg.dbobj.SnpSession.treatSessionPreTrt(SnpSession.java)
     at com.sunopsis.dwg.dbobj.SnpSession.treatSession(SnpSession.java)
     at com.sunopsis.dwg.cmd.DwgCommandScenario.treatCommand(DwgCommandScenario.java)
     at com.sunopsis.dwg.cmd.DwgCommandBase.execute(DwgCommandBase.java)
     at com.sunopsis.dwg.cmd.e.i(e.java)
     at com.sunopsis.dwg.cmd.h.y(h.java)
     at com.sunopsis.dwg.cmd.e.run(e.java)
     at java.lang.Thread.run(Thread.java:595)
In the BPEL Console the result is OK and process complete, but in the INVOKE scenario send message:
<messages><ODI_REQUEST><part xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" name="part1"><invokeScenarioRequest xmlns="xmlns.oracle.com/odi/OdiInvoke/">
*<RepositoryConnection xmlns=""*
<JdbcDriver>oracle.jdbc.driver.OracleDriver</JdbcDriver>
<JdbcUrl>jdbc:oracle:thin:@192.168.1.109:1521:ORCL</JdbcUrl>
<JdbcUser>dimaster</JdbcUser>
<JdbcPassword>sabr0sa</JdbcPassword>
<OdiUser>SUPERVISOR</OdiUser>
<OdiPassword>SUNOPSIS</OdiPassword>
<WorkRepository>TESTWORKREP1</WorkRepository>
</RepositoryConnection>
*<Command xmlns="">*
<ScenName>P_TRASPASOSOP09</ScenName>
<ScenVersion>2</ScenVersion>
<Context>Global</Context>
<LogLevel>5</LogLevel>
<SyncMode>0</SyncMode>
<SessionName/>
<Keywords/>
<Variables>
<Name/>
<Value xmlns:ns1="http://xmlns.oracle.com/Recepcion">
<ns1:Escenario>P_TRASPASOSOP09</ns1:Escenario>
<ns1:Version>2</ns1:Version>
<ns1:Contexto>Global</ns1:Contexto>
<ns1:ID>1</ns1:ID>
<ns1:NivelLogeo>5</ns1:NivelLogeo>
</Value>
</Variables>
</Command>
*<Agent xmlns="">*
<Host>192.168.1.109</Host>
<Port>20910</Port>
</Agent>
</invokeScenarioRequest>
</part></ODI_REQUEST><ODI_RESPONSE><part xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" name="part1"><odi:invokeScenarioResponse xmlns:odi="xmlns.oracle.com/odi/OdiInvoke/">
<odi:CommandResultType>
<odi:Ok>true</odi:Ok>
<odi:SessionNumber>445000</odi:SessionNumber>
</odi:CommandResultType>
</odi:invokeScenarioResponse>
</part></ODI_RESPONSE></messages>

Unable to invoke a EJB from a BPEL process

I am unable to invoke a EJB from a BPEL process. Whenever I try to test it from the oracle EM, I get the below exception. I am using WebLogic 10.3.3, SOA suite 11.1.1.3 and JDev 11.1.1.3 .
This is what I see from the EM....
Non Recoverable System Fault :
javaInterface attribute for the binding is missing or the inteface class is not available.
Below is a part of the stack trace from the soa server log…
Caused By: oracle.classloader.util.AnnotatedClassNotFoundException:
Missing class: com.abc.GreetingEJBBean
Dependent class: oracle.integration.platform.blocks.ejb.SDOEjbReferenceD
elegateImpl
Loader: sun.misc.Launcher$AppClassLoader@20929799
Code-Source: /C:/Oracle_latest/Middleware/home_11gR1/Oracle_SOA1/soa
/modules/oracle.soa.fabric_11.1.1/fabric-runtime.jar
Configuration: /C:/Oracle_latest/Middleware/home_11gR1/Oracle_SOA1/soa
/modules/oracle.soa.fabric_11.1.1/fabric-runtime.jar
Piece of xml from the composite.xml
<reference name="GreetingService"
ui:wsdlLocation="http://123.45.218.140:7001/GreetingEJBBean/GreetingEJBBeanService?wsdl">
<interface.wsdl interface="http://abc.com/#wsdl.interface(GreetingEJBBean)" />
<binding.ejb uri="GreetingEJB-GreetingEJB-GreetingEJB"
javaInterface="com.abc.GreetingEJB"/>
</reference>
Looks like its not able to find the javaInterface mentioned above.
I have a simple EJB with one business method and a very simple BPEL process.
@Stateless(name = "GreetingEJB", mappedName = "GreetingEJB-GreetingEJB-GreetingEJB")
@WebService
public class GreetingEJBBean implements GreetingEJB {
public GreetingEJBBean() {
public String greetUser(String name){
return ("Hello " + name);
Any help would be greatly appreciated.

I haven't tried from a BPEL process, but I have had success (as in Lucas's blogs) of using services and references as EJB Java Interface. This is with EJB java interfaces solely of base types (i.e. String foo(String s)).
At high level here's what I have noted so far:
1. Per Lucas's blog, @javaInterface is not being added to the ejb.binding automatically but it's not clear to me when this is and is not required given that interface.java is specified for the reference or service. Would interface.java and @javaInterface ever be different? I've been adding @javaInterface manually anyways since Lucas is a smart guy and I'd rather avoid errors. :-)
2. Dropping an EJB interface jar in SCA-INF/lib works, but I've had the problem that the JDeveloper SOA Plugin doesn't see those classes until I stop and restart JDeveloper. Until then, I'm confronted with the java->wsdl mapping error. I was sort of primed to figure this one out since I ran into similar issues with SOA SpringBean components.
3. Dropping EJB interface source in SCA-INF/src is more reliable, because then I can build the project (i.e. create SCA-INF/classes) and the JDeveloper SOA Plugin seems to resolve these brand new classes immediately.
4. I've tried to invoke an EJB java-interface reference with a slightly complicated java interface (a class parameter with some fields, one of which is an array of another class). The auto-generated WSDL doesn't look exactly right to me (but I'm new to JAXB). Mediator maps to it just fine and the project compiles and deploys normally but fails at runtime. I have not researched in depth. It's not clear to me from the documentation and release notes whether I should expect for it to work, or whether I should expect to have to create my own JAXB mapping. If the latter, I really need a good example!

Unable to invoke EJB from a BPEL process.

Hello all
I am running BPEL process manager over weblogic 8.1 App server. I am trying to invoke a simple stateless session bean from a synchronous BPEL process. I have created a WSDL for this EJB with appropriate binding and service elements.
I am able to build my BPEL sync process and deploy it. But, when I run the process and invoke the EJB, I am getting the following exception-
BPEL Fault: {http://schemas.oracle.com/bpel/extension}bindingFaultCould not create instance for home 'ClusterableRemoteRef(-3059145150938040994S:172.26.210.17:[9700,9700,-1,-1,9700,-1,-1,0,0]:myorabpel:orabpelServer [-3059145150938040994S:172.26.210.17:[9700,9700,-1,-1,9700,-1,-1,0,0]:myorabpel:orabpelServer/288])/288'; nested exception is:
java.lang.NoSuchMethodException: com.carlson.sample.HelloWorldSessionBean_n4vx3i_HomeImpl_812_WLStub.create()
I have a home interface for the EJB which has a 'create' method and my session bean has a ejbCreate method. I am using weblogic.appc to create the stubs and skeletons for the EJB.
Has anyone tried this ?? The tutorial in the download 702.bindings/EJBBinding does something similar to this. But, I am having problems with that too.
Any comments, advice, sample code will be helpful.
Thanks a bunch
- Mahesh :)

I have deployed my Bean Managed Persistance Entity Bean in Weblogic 8.1 App Server. Trying to access the ejb from Synchronous BPEL process. I tried in two ways
1. By accessing the ejb directly from BPEL process, writing the following code in BPEL process
<bpelx:exec xmlns:bpelx="http://schemas.oracle.com/bpel/extension" language="java" version="1.4" name="InventoryEJB">
               <![CDATA[
     // Java code snippet
     try{
     Hashtable properties = new Hashtable();
          properties.put(InitialContext.INITIAL_CONTEXT_FACTORY,
"weblogic.jndi.WLInitialContextFactory");
          properties.put(InitialContext.PROVIDER_URL, "t3://PCIIB07447:7001");
          InitialContext context = new InitialContext(properties);
          InventoryHome home = (InventoryHome) context.lookup("Inventory");
          InventoryRemote remote = home.create();
          int status = remote.getInventory("Chevrolet","2-Door Coupes","Chevy Cobalt",5);
          addAuditTrailEntry("Status is: " + status);
setVariableData("output", "payload",
"/status", new Integer(status));
catch(Exception e){}
     ]]>
          </bpelx:exec>
Also copied the interface files in system\classes directory. I got the expected output but i am not able to view the "Visual Flow". Getting the following error in my BPEL server console
<Sep 9, 2004 12:46:51 PM IST> <Warning> <RMI> <BEA-080003> <RuntimeException thr
own by rmi server: weblogic.management.internal.RemoteMBeanServerImpl.invoke(Lja
vax.management.ObjectName;Ljava.lang.String;[Ljava.lang.Object;[Ljava.lang.Strin
g;)
weblogic.management.NoAccessRuntimeException: Access not allowed for subject: p
rincipals=[], on ResourceType: ServerConfig Action: execute, Target: lookupServe
rRuntime.
weblogic.management.NoAccessRuntimeException: Access not allowed for subject: pr
incipals=[], on ResourceType: ServerConfig Action: execute, Target: lookupServer
Runtime
at weblogic.management.internal.SecurityHelper$IsAccessAllowedPrivilegeA
ction.wlsRun(SecurityHelper.java:564)
at weblogic.management.internal.SecurityHelper$IsAccessAllowedPrivilegeA
ction.run(SecurityHelper.java:456)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(Authenticate
dSubject.java:317)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:
118)
at weblogic.management.internal.SecurityHelper.isAccessAllowed(SecurityH
elper.java:350)
at weblogic.management.internal.RemoteMBeanServerImpl.private_invoke(Rem
oteMBeanServerImpl.java:946)
at weblogic.management.internal.RemoteMBeanServerImpl.invoke(RemoteMBean
ServerImpl.java:908)
at weblogic.management.internal.RemoteMBeanServerImpl_WLSkel.invoke(Unkn
own Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:477)
at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:420)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(Authenticate
dSubject.java:353)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:
144)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.jav
a:415)
at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest
.java:30)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
2. The other way i used WSIF frame work, but i could not resolved.
Thanks for your help in advance.

Error while invoking ESB process from a BPEL process

Hi all
We have a requirement to call an ESB process from a BPEL process. We are using an adapter wth the ESB's WSDL url. After deploying the BPEL process, the registered ESB is getting called for most values while suddenly some values return the followign error
*"exception on JaxRpc invoke: HTTP transport error: javax.xml.soap.SOAPException: java.security.PrivilegedActionException: javax.xml.soap.SOAPException: Message send failed: Connection reset"*
The catch here is, if we re-run the process with the same values again, the ESB is called successfully! How is it possible for a process to error out and run normally for the same inputs ?
What could be the possible fix for this? I am thankful for any inputs on this.
Vijay

Hi Vijay,
This is a bug and you can refer the metalink note:
"Applying Patch 7445876 Results in Error "java.lang.NullPointerException". [ID 942575.1]" for reference.
Also you can refer the following link:
"http://puchaanirudh.blogspot.com/2008/12/exception-on-jaxrpc-invoke-http.html" also.
Thanks,
Vishwanath.

Invoking JDev bpel process from Eclipse BPEL Process?

Is it possible to invoke a bpel process (with dbadapter) developed in JDev from a bpel process created in Eclipse (Designer)?

I was unsuccessful.
Scenario:
I was trying to invoke jdev bpel process (that had a database adapter to update the database) from Eclipse bpel process (since we do not have adapters in Eclipse designer).
The namespace wasn't known by Eclipse( some schema missing?) and therefore we couldn't compile it.

Invoking bpel process from another bpel process in same app server

Hi,
When I invoke a bpel process from another bpel process in the same oracle AS
1. Is it a SOAP call or is there any optimization?
2. If there is some optimization where can I configure this?
3. Is there any similar optimizations if I invoke a bpel process from a
java application deployed in the same server? If so can you please provide
a sample?
Thanks for your help
Raj

By default the BPEL 10.1.2, it will do a local call to the process. It will not execute a SOAP request, no network access is done.
It can be configured at domain level:
Parameter: optSoapShortcut (SOAP local optimization)
Turns on "short-cut" for local SOAP request; local SOAP calls are normally done via an internal call instead of sending a message through the SOAP stack.
The default behavior for the engine is to optimize all. To disable optimization specify a value other than "true" or "yes".

Invoking Session EJB (with WSIF binding) from a BPEL process

Hi,
I am invoking a stateless session bean from a bpel process. The bpel process is throwing:
Failed to lookup EJB home using JNDI name 'ejb/visilient/BPELHelper'; nested exception is:
java.lang.NullPointerException
I can see the ejb jndi name under 'default' app.
Any ideas?
TIA

It is a lovely sample... However, it doesn't cover Complex Types and Exception handling. It would be nice if each example was thorough. Would be a great help.
What I was hoping to achieve is this:
1) Have an EJB deployed
2) Use WSIF for BPEL Processes.
3) Use Web Service interface for AJAX calls etc.
I was hoping that this would be the exact code base and that only a single EJB would be deployed.
So far, it looks like JDeveloper will only support Java WSIF bindings. No EJB Bindings. It also looks like JAXRPC is the best supported WS interface. With that in mind, it deploys a seperate subset of the EJB. Thus causing two seperate deployments. I am working on trying all this out over the next couple days. See where I get.
Anyways, do you have any recommendation for accomplishing what I am wanting to do? 1 deployed EJB, with a WS interface and allowing WSIF bindings. Any other references for me to look at? Should I not be thinking about using JDeveloper for any of the WSDL generation and do all this manually for now?
Thanks,
BradW

How to invoke a custom adapter from a BPEL process

Hi guys,
I've implemented a custom outbound adapter and deployed successfully on Weblogic V.10.3.4.
My current installation also consists of Oracle SOA Suite 11g / JDeveloper 11g (11.1.1.4.0)
In the Weblogic administrator's console,
*1.* I navigated to:
Summary of Deployments -> AdapterName -> Configuration -> Outbound Connection Pools
*2.* Selected: javax.resource.cci.ConnectionFactory and added new JNDI name for Outbound Connection Instance: "*eis/HelloWorld*"
My task is to invoke the custom adapter from a BPEL process.
I altered the customAdapter-config.xml so as to be able to use custom adapter wizard from JDeveloper's "Service Adapters" palette,
and fullfilled the custom adapter wizard's fields accordingly. The 3rd step of the wizard requires Connection Information.
I added: "*eis/HelloWorld*" in the "*Connection Factory Location*" field.
Deployed BPEL process successfully, but testing failed due to binding.jca-12510 error:
"The JCA Binding Component was unable to establish an outbound JCA CCI connection due to the following issue: BINDING.JCA-12510 JCA Resource Adapter location error. Unable to locate the JCA Resource Adapter via .jca binding file element <connection-factory/> The JCA Binding Component is unable to startup the Resource Adapter specified in the <connection-factory/> element: location='eis/HelloWorld'. The reason for this is most likely that either 1) the Resource Adapters RAR file has not been deployed successfully to the WebLogic Application server or 2) the '<jndi-name>' element in weblogic-ra.xml has not been set to eis/HelloWorld. In the last case you will have to add a new WebLogic JCA connection factory (deploy a RAR). Please correct this and then restart the Application Server "I tried to apply (just for testing) "eis/FileAdapter" in the "Connection Factory Location" field of the custom adapter wizard,
and BPEL successfully invoked the adapter.
Any ideas ?
Thanks,
George

George, What deployment do you have this associated with?
- D.J.

How to invoke an OSB service from a BPEL process

I need help, to figure out how to invoke an OSB proxy service from a BPEL process.
I found a blog which exactly does that; but I am unable to get it to work. I get the following error on my BPEL console. We are on OSB10gR3 and SOA 10134.
"com.bea.wli.sb.transports.TransportException: Unknown error while processing message for service ProxyService DWIntegrations/ProxyService/PeopleServiceBus"
Any help will be greatly appreciated.
Regards,
BP

It really comes down to the proxy service on the OSB. Is it invoked by a WSDL? If so you should be able to take the endpoint defined in the proxy service messaging configuration and use that URL. You also need to use the sb transport type.
Can you also post the blog you used, then we can put it into context.
also have a look at this link.
http://download.oracle.com/docs/cd/E13159_01/osb/docs10gr3/bpelpmtransport/transport.html#wp1116011
cheers
James

How to obtain response from asyn bpel process invoked through java

I need to get the response from Asynchronous bpel process which im invoking through java using DeliveryPost method whose return type is void.

I was able to write java code for the above process
the code is here
NormalizedMessage nm = new NormalizedMessage( );
String uniqueBpelId = com.collaxa.cube.util.GUIDGenerator.generateGUID();
java.util.Map msgProps = new HashMap();
// NormalizedMessage res = deliveryService.request("OraFormsService", "initiate", nm);
//deliveryService.post(null,null,null,null);
msgProps.put("conversationId",uniqueBpelId);
nm.setProperty("conversationId",uniqueBpelId);//to set the property for this message
nm.addPart("payload",xml1);//to add to the payload of this message
deliveryService.post("OraFormsService", "initiate", nm);
// System.out.println("con1 "+IDeliveryConstants.STATE_HANDLED);
StringBuffer buf = new StringBuffer();
WhereCondition cond;
cond = new WhereCondition(buf.append(SQLDefs.IM_state).append( " = " ).append(IDeliveryConstants.STATE_UNRESOLVED ).toString() );
//cond = WhereConditionHelper.whereInstancesOpen();
IInvokeMetaData imd[] = locator.listInvokeMessages(cond);
String ids[] = new String[imd.length];
// print out the partial process information
// for processes in manual recovery status on invoke
for (int i = 0; i < imd.length; i++)
System.out.println("ConversationId=" +
imd.getConversationId());
System.out.println("ProcessId=" +
imd[i].getProcessId());
System.out.println("State=" + imd[i].getState());
ids[i] = imd[i].getConversationId();
Thanks for the Help

Trying to throw fault from one BPEL process to another

We are trying to throw a fault from one BPEL process to another and apparently are experiencing a common problem. That is, the invoking process times out and never receives the fault.
Likely a beginner's mistake is at fault (pun intended).
Below are samples of a simple "Hello World" process that tries to throw the fault.
snippet of pbel file....
<process name="HelloJavaWorldSynchronous"
targetNamespace="http://xmlns.oracle.com/HelloJavaWorldSynchronous"
xmlns="http://schemas.xmlsoap.org/ws/2003/03/business-process/"
xmlns:xp20="http://www.oracle.com/XSL/Transform/java/oracle.tip.pc.services.functions.Xpath20"
xmlns:bpws="http://schemas.xmlsoap.org/ws/2003/03/business-process/"
xmlns:ns1="http://helloworldjavaproject/"
xmlns:ldap="http://schemas.oracle.com/xpath/extension/ldap"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:client="http://xmlns.oracle.com/HelloJavaWorldSynchronous"
xmlns:bpelx="http://schemas.oracle.com/bpel/extension"
xmlns:ora="http://schemas.oracle.com/xpath/extension"
xmlns:orcl="http://www.oracle.com/XSL/Transform/java/oracle.tip.pc.services.functions.ExtFunc">
<faultHandlers>
<catchAll>
<sequence name="Sequence_1">
<assign name="Assign_3">
<copy>
<from expression="12345"/>
<to variable="FaultVar" part="code"/>
</copy>
<copy>
<from expression="'Hello fault summary'"/>
<to variable="FaultVar" part="summary"/>
</copy>
<copy>
<from expression="'Hello test detail'"/>
<to variable="FaultVar" part="detail"/>
</copy>
</assign>
<throw name="Throw_2" faultName="client:myFault"
faultVariable="FaultVar"/>
</sequence>
HelloJavaWorldSynchronous.wsdl file
<definitions
name="HelloJavaWorldSynchronous"
targetNamespace="http://xmlns.oracle.com/HelloJavaWorldSynchronous"
xmlns="http://schemas.xmlsoap.org/wsdl/"
xmlns:ns1="http://schemas.oracle.com/bpel/extension"
xmlns:plnk="http://schemas.xmlsoap.org/ws/2003/05/partner-link/"
xmlns:client="http://xmlns.oracle.com/HelloJavaWorldSynchronous"
>
<import namespace="http://schemas.oracle.com/bpel/extension" location="RuntimeFault.wsdl";/>
<types>
<schema xmlns="http://www.w3.org/2001/XMLSchema">
<import namespace="http://xmlns.oracle.com/HelloJavaWorldSynchronous" schemaLocation="HelloJavaWorldSynchronous.xsd";/>
</schema>
</types>
<message name="HelloJavaWorldSynchronousRequestMessage">
<part name="payload" element="client:HelloJavaWorldSynchronousProcessRequest"/>
</message>
<message name="HelloJavaWorldSynchronousResponseMessage">
<part name="payload" element="client:HelloJavaWorldSynchronousProcessResponse"/>
</message>
<portType name="HelloJavaWorldSynchronous">
<operation name="process">
<input message="client:HelloJavaWorldSynchronousRequestMessage"/>
<output message="client:HelloJavaWorldSynchronousResponseMessage"/>
<fault name="myFault" message="ns1:RuntimeFaultMessage"/>
</operation>
</portType>
<plnk:partnerLinkType name="HelloJavaWorldSynchronous">
<plnk:role name="HelloJavaWorldSynchronousProvider">
<plnk:portType name="client:HelloJavaWorldSynchronous"/>
</plnk:role>
</plnk:partnerLinkType>
</definitions>
The standard RuntimeFault.wsdl file (RuntimeFaultMessage message is defined in here, so I don't need a message in HelloJavaWorldSynchronous.wsdl. Do I?)
<?xml version="1.0"; encoding="UTF-8"?>
<definitions name="RuntimeFault"
targetNamespace="http://schemas.oracle.com/bpel/extension"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns="http://schemas.xmlsoap.org/wsdl/">
<message name="RuntimeFaultMessage">
<part name="code" type="xsd:string"/>
<part name="summary" type="xsd:string"/>
<part name="detail" type="xsd:string"/>
</message>
</definitions>
But when we invoke the process, after the standard 45 seconds timeout, we still get...
<Faulthttp://schemas.xmlsoap.org/soap/envelope/>
<faultcode>env:Server</faultcode>
<faultstring>com.oracle.bpel.client.delivery.ReceiveTimeOutException: Waiting for response has timed out. The conversation id is f290d62d2ad31aa6:-49eb76f4:124eb51622a:-7c91. Please check the process instance for detail.</faultstring>
</Fault>
The console audit below might hold a clue. I noticed the mesage BPELFault" has not been caught by a catch block at the end.
<catchAll>
<sequence>
Assign_3
[2009/11/13 11:18:32] Updated variable "FaultVar" More...
-<FaultVar>
-<part xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" name="code">
<code xmlns="" xmlns:def="http://www.w3.org/2001/XMLSchema" xsi:type="def:string" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">12345
</code>
</part>
-<part xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" name="summary">
<summary xmlns="" xmlns:def="http://www.w3.org/2001/XMLSchema" xsi:type="def:string" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/>
</part>
-<part xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" name="detail">
<detail xmlns="" xmlns:def="http://www.w3.org/2001/XMLSchema" xsi:type="def:string" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/>
</part>
</FaultVar>
[2009/11/13 11:18:32] Updated variable "FaultVar" More...
-<FaultVar>
-<part xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" name="code">
<code xmlns="" xmlns:def="http://www.w3.org/2001/XMLSchema" xsi:type="def:string" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">12345
</code>
</part>
-<part xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" name="summary">
<summary xmlns="" xmlns:def="http://www.w3.org/2001/XMLSchema" xsi:type="def:string" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">Hello fault summary
</summary>
</part>
-<part xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" name="detail">
<detail xmlns="" xmlns:def="http://www.w3.org/2001/XMLSchema" xsi:type="def:string" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/>
</part>
</FaultVar>
[2009/11/13 11:18:32] Updated variable "FaultVar" More...
-<FaultVar>
-<part xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" name="code">
<code xmlns="" xmlns:def="http://www.w3.org/2001/XMLSchema" xsi:type="def:string" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">12345
</code>
</part>
-<part xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" name="summary">
<summary xmlns="" xmlns:def="http://www.w3.org/2001/XMLSchema" xsi:type="def:string" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">Hello fault summary
</summary>
</part>
-<part xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" name="detail">
<detail xmlns="" xmlns:def="http://www.w3.org/2001/XMLSchema" xsi:type="def:string" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">Hello test detail
</detail>
</part>
</FaultVar>
Throw_2 (faulted)
[2009/11/13 11:18:32] "{http://xmlns.oracle.com/HelloJavaWorldSynchronous}myFault" has been thrown. More...
-<myFault xmlns="http://xmlns.oracle.com/HelloJavaWorldSynchronous">
-<part name="code">
<code xmlns="" xmlns:def="http://www.w3.org/2001/XMLSchema" xsi:type="def:string" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">12345
</code>
</part>
-<part name="summary">
<summary xmlns="" xmlns:def="http://www.w3.org/2001/XMLSchema" xsi:type="def:string" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">Hello fault summary
</summary>
</part>
-<part name="detail">
<detail xmlns="" xmlns:def="http://www.w3.org/2001/XMLSchema" xsi:type="def:string" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">Hello test detail
</detail>
</part>
</myFault>
</sequence>
</catchAll>
[2009/11/13 11:18:32] "BPELFault" has not been caught by a catch block.
[2009/11/13 11:18:32] BPEL process instance "570162" cancelled

Thanks very much for this answer. It was right on.
You wanted to know "how (I) get on". Funny you should ask. Believe it or not, I had figured out the problem on my own just about the time you were posting your reply (of course, this is a bit too convenient. No one will ever believe me).
But the answer leads to another question. What is the Throw activity for, if not to throw an error to the calling process? Is it only used to throw within scope of the process its self?
I am probably biased by the Java world I am coming from, but Throw feels like it should terminate the process (without side effects like a big red mark in the console) bubble up the fault to the calling process who can catch it (if so desired). Using the reply we must explicitly Terminate (which includes that unsightly red mark).
Is there any way to get this behavior from the Throw, or should we just reprogram the "wetware" and learn a new paradigm?
Is there any way to end a process without marking it with a red flag that suggests something went wrong?

How can we call a OSB proxy service from a BPEL process?

Hi,
I want to call a OSB proxy service from a BPEL process. Can you please explain me the procedure?

Get the wsdl of the OSB proxy service and create webservice parnerlink in BPEL based on this wsdl to invoke the service
To form the wsdl url, copy the Endpoint URI configured to the proxy service(just click on the proxy service in the console) from the sbconsole - /ATHGPUM_GlidePathService/ProxyService/ATHGPUM_GlidePathProxyService
Pre append <<protocol://OSB Hostname:OSB Port>> - http://localhost:8000/ and post append with ?WSDL
The final WSDL url look like - http://localhost:8000/ATHGPUM_GlidePathService/ProxyService/ATHGPUM_GlidePathProxyService?WSDL
Regards
Albin I

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.

How to Get the Parent Process ID from Child BPEL Process

Hi All,
We have a requirement to get the Parent BPEL Process ID from Child BPEL Process. One way is we can pass the Parent BPEL process ID from Parent BPEL Process to Child BPEL process. Is there any standard function available to get the Parent BPEL process ID from Child Process?
P.S: We are using BPEL 10.1.3 Version.
Please share any info on this.
Thanks in Advance,
Saravana

Hi Saravana,
The existing methods in 10.1.3x allow a following (a bit of a convoluted way):
In a BPEL Java embedding activity, you can use the following code to get the parentProcessname:
String parentInstanceId = getParentId();
String parentProcessname = getLocator().locator.lookupInstance(parentInstanceId).getProcess().getProcessId().getProcessId();Hope this helps,
Regards,
Shanmu
http://www.prshanmu.com/articles/

Problem invoking from a BPEL process webservice client

Similar Messages

Maybe you are looking for