Calling Receive activity in mid of BPEL process
HI,
I have a requirement where i need to read data from XML file and store into Database.
I am using File Adapter and Data base adapter for this purpose. I am able to do this operation by having one Receive activity (To read file) and one Invoke activity (To write on to DB). whenever I deploy process an instance will be created. but i do not get test URL.
I tried to call receive activity inside BPEL process which has no input. This gives me test URL. but Receive activity to read file is not getting initiated. it'll be pending.
How to solve this ?
Thanks.
Hi,
First thing you need to decide is, how you want your BPEL to start, do you want that to start by calling it (this means you need to expose it as a web service) or start it whenever a file is available (file adapter will be a service and you are doing polling here). So, if you are doing the second thing, for that composite in the EM console, there will be no test button, because it is not exposed as a webservice. If you do like this, there will be a receive activity inside the BPEL (first activity in BPEL). If you want your BPEL to start whenever a file is available as well as exposed as a web service, you need ot define the BPEL based on the WSDL of file adapter service as well as exposing it a sa web service. If you do this, you need to keep the on Message activity inside your BPEL and design your flow accordingly. and in file adapter, you also have an option of reading the file outbound (synchronous read operation), but this doesn't solve your purpose i guess...
Let me know...
Thanks,
N
Similar Messages
-
Invoke OnMessage activity of a running BPEL process instance...
Hi,
We are using Oracle BPEL 10.1.2.0.2. I am willing to invoke a running instance of a BPEL process (Timer) in following scenario:
The 'Timer' BPEL Process gets initiated, and logs its instance-id into the database
'Timer' process waits on an OnMessage activity for another process to invoke it
Another BPEL process selects the instance-id of 'Timer' process from the database
The question is: in the above scenario, can the 2nd BPEL process invoke the OnMessage activity of the Timer BPEL process. I did search through the Locator API but was unable to find a method which can invoke a running BPEL instance.
I am not willing to use correlation here because correlation does not guaranty the invocation of the target BPEL process and also does not generate any error if no instance gets invoked.
Thanks,
Upendra Jariya.JDK 5.0 includes sample code for java.lang.management API in the <JDK>/demo/management directory. In particular, demo/management/VerboseGC demonstrates how to use the java.lang.management API to print GC statistics in a similar way to -verbose:gc.
You can reference this demo program and make appropriate modification, for example, just to call java.lang.management.MemoryMXBean.setVerbose() operation to turn on/off the -verbose:gc tracing. -
Is it possible to have two receive activities in a single bpel process
Hi,
I have a requirement where I will get a input from a service and I have to pass this input dynamically to file adapter which then retrieved the files from a location based on the input provided and passes it to other service.
I have used one receive activity for getting input parameters and other receive activity for getting files activity, but unfortunately it is not allowing me to do so. How can I design the process,
1. I will get an input from a service.
2. FA has to be invoked for getting files from location specified ( I know that dynamic values can be set inside properties tab), but confused on how to work with two receive activities.
3. And the retrieved files has to be sent to a service.
Thanks,
Edited by: kameshb on Mar 29, 2013 9:59 AMHi Kamesh,
Read operation is used to poll files from a specified directory, in most cases it will be first activity(receive) of your BPEL and will create a new instance for you(else use correlation for mid process receive).
As in your case you are dynamically passing input to FA to read a specific file in mid of your process, it should be sync read operation (as suggested by Deepak) wit an invoke activity.
Thanks,
Faiz
Edited by: Faiz Haq on Mar 30, 2013 1:42 AM
Edited by: Faiz Haq on Mar 30, 2013 1:46 AM -
New problem calling PL/SQL based WS from BPEL process
I have created a webservice based on a PL/SQL package based function with JDeveloper and deployed the web service on the BPEL OC4J server.
Calling the web service endpoint directly from internet explorer works fine.
I have also created and deployed a BPEL process to call this web service. When i run the process it completes normally but returns an Oracle error in the out-variable: "Ora-06502 Numerical value error".
Through my PL/SQL logging i can see that the input-variable to the PL/SQL function is empty (so when i try to use this value it gives me the Ora-06502 error).
When i check the audit trail of the BPEL process instance i find that the assignment of the input variable is ok. This input variable is used in the invokation of the web service (and at this point still has the proper value).
What can be wrong? (the only part i cannot trace is the working of the Java stub created by JDeveloper).
Any ideas?
thanks, BartThis is the complete stack trace:
<2004-12-01 10:48:52,012> <DEBUG> <default.collaxa.cube.ws> <WSInvocationManager::invoke> operation: CataLog
<2004-12-01 10:48:52,012> <DEBUG> <default.collaxa.cube.ws> <WSInvocationManager::invoke> inputContainer: {InputParameters=<CATLOG xmlns="http://xmlns.oracle.com/pcbpel/adapter/db/EBILLING/CATALOG/"><ID_AZIENDA>134</ID_AZIENDA><ID_PROGETTO>134</ID_PROGETTO><CAPTURE_DATETIME>1959</CAPTURE_DATETIME><FULLNAME>lkjh</FULLNAME><PATHNAME>kjsf</PATHNAME><FILENAME>kjsf</FILENAME><DESTINATION_PATH>kjsf</DESTINATION_PATH><MOVE_DATETIME>1959</MOVE_DATETIME><SIZE_BYTES>134</SIZE_BYTES><LAST_WRITE>1959</LAST_WRITE><ID_THOR>2345234</ID_THOR><SNAPSHOT_PATH>kjsf</SNAPSHOT_PATH></CATLOG>}
<2004-12-01 10:48:52,013> <DEBUG> <default.collaxa.cube.ws> <WSInvocationManager::invoke> callProps: {is-initial-call=true, parentId=5602, process-id=StoredProcedure, rootId=5602, conversationId=bpel://localhost/default/StoredProcedure~1.0/5602-BpInv0-BpSeq0.3-3, location=null, priority=0, work-item-key=5602-BpInv0-BpSeq0.3-3, domain-id=default, revision-tag=1.0}
<2004-12-01 10:48:52,013> <DEBUG> <default.collaxa.cube.ws> <WSInvocationManager::invoke> def is http://orcldemo.localdomain:9700/orabpel/default/StoredProcedure/StoredProcedureOutbound.wsdl
<2004-12-01 10:48:52,014> <DEBUG> <default.collaxa.cube.ws> <WSIFInvocationHandler::invoke> opName=CataLogportTypeQn={http://xmlns.oracle.com/pcbpel/adapter/db/test/CataLog/}CataLog_pttserviceQn={http://xmlns.oracle.com/pcbpel/adapter/db/test/CataLog/}CataLog
<2004-12-01 10:48:52,015> <DEBUG> <default.collaxa.cube.ws> <AdapterFramework::Outbound> http://orcldemo.localdomain:9700/orabpel/default/StoredProcedure/StoredProcedureOutbound.wsdl[{http://xmlns.oracle.com/pcbpel/adapter/db/test/CataLog/}CataLog_ptt]: Locating jndiAdapterInstance eis/CatapultDBLog
<2004-12-01 10:48:52,015> <DEBUG> <default.collaxa.cube.ws> <AdapterFramework::Outbound> Instantiating outbound JCA interactionSpec oracle.tip.adapter.db.DBStoredProcedureInteractionSpec
<2004-12-01 10:48:52,016> <DEBUG> <default.collaxa.cube.ws> <AdapterFramework::Outbound> Populating outbound JCA interactionSpec oracle.tip.adapter.db.DBStoredProcedureInteractionSpec with properties: {ProcedureName=CATALOG, SchemaName=EBILLING}
<2004-12-01 10:48:52,234> <DEBUG> <default.collaxa.cube.ws> <AdapterFramework::Outbound> Instantiating outbound JCA interactionSpec oracle.tip.adapter.db.DBStoredProcedureInteractionSpec
<2004-12-01 10:48:52,235> <DEBUG> <default.collaxa.cube.ws> <AdapterFramework::Outbound> Populating outbound JCA interactionSpec oracle.tip.adapter.db.DBStoredProcedureInteractionSpec with properties: {ProcedureName=CATALOG, SchemaName=EBILLING}
<2004-12-01 10:48:52,294> <INFO> <default.collaxa.cube.ws> <AdapterFramework::Outbound> http://orcldemo.localdomain:9700/orabpel/default/StoredProcedure/StoredProcedureOutbound.wsdl[CataLog_ptt::CataLog(null)] Invoking JCA outbound Interaction
<2004-12-01 10:48:52,296> <DEBUG> <default.collaxa.cube.ws> <Database Adapter::Outbound> <oracle.tip.adapter.db.TopLinkLogger log> client acquired
<2004-12-01 10:48:52,297> <ERROR> <default.collaxa.cube.ws> <AdapterFramework::Outbound> http://orcldemo.localdomain:9700/orabpel/default/StoredProcedure/StoredProcedureOutbound.wsdl[CataLog_ptt::CataLog(null)] Could not invoke 'CataLog' due to: Encountered an unexpected exception while trying to execute the interaction.
An unexpected exception occurred while trying to execute the interaction for invoking the API.
Analyze and correct the error if possible. Contact oracle support if error is not fixable.
<2004-12-01 10:48:52,299> <ERROR> <default.collaxa.cube.ws> <AdapterFramework::Outbound> ORABPEL-11813
Encountered an unexpected exception while trying to execute the interaction.
An unexpected exception occurred while trying to execute the interaction for invoking the API.
Analyze and correct the error if possible. Contact oracle support if error is not fixable.
at oracle.tip.adapter.db.DBInteraction.executeStoredProcedure(DBInteraction.java:429)
at oracle.tip.adapter.db.DBInteraction.execute(DBInteraction.java:140)
at oracle.tip.adapter.fw.wsif.jca.WSIFOperation_JCA.executeRequestResponseOperation(WSIFOperation_JCA.java:395)
at com.collaxa.cube.ws.WSIFInvocationHandler.invoke(WSIFInvocationHandler.java:356)
at com.collaxa.cube.ws.WSInvocationManager.invoke(WSInvocationManager.java:288)
at com.collaxa.cube.ws.WSInvocationManager.invoke(WSInvocationManager.java:134)
at com.collaxa.cube.engine.ext.wmp.BPELInvokeWMP.__invoke(BPELInvokeWMP.java:541)
at com.collaxa.cube.engine.ext.wmp.BPELInvokeWMP.__executeStatements(BPELInvokeWMP.java:284)
at com.collaxa.cube.engine.ext.wmp.BPELActivityWMP.perform(BPELActivityWMP.java:178)
at com.collaxa.cube.engine.CubeEngine.performActivity(CubeEngine.java:3438)
at com.collaxa.cube.engine.CubeEngine.handleWorkItem(CubeEngine.java:1818)
at com.collaxa.cube.engine.dispatch.message.instance.PerformMessageHandler.handleLocal(PerformMessageHandler.java:75)
at com.collaxa.cube.engine.dispatch.DispatchHelper.handleLocalMessage(DispatchHelper.java:85)
at com.collaxa.cube.engine.dispatch.DispatchHelper.sendMemory(DispatchHelper.java:138)
at com.collaxa.cube.engine.CubeEngine.endRequest(CubeEngine.java:5522)
at com.collaxa.cube.engine.CubeEngine.createAndInvoke(CubeEngine.java:1221)
at com.collaxa.cube.engine.delivery.DeliveryService.handleInvoke(DeliveryService.java:480)
at com.collaxa.cube.engine.bean.DeliveryBean.handleInvoke(DeliveryBean.java:307)
at IDeliveryLocalBean_StatelessSessionBeanWrapper16.handleInvoke(IDeliveryLocalBean_StatelessSessionBeanWrapper16.java:1791)
at com.collaxa.cube.engine.dispatch.message.invoke.InvokeInstanceMessageHandler.handle(InvokeInstanceMessageHandler.java:36)
at com.collaxa.cube.engine.dispatch.DispatchHelper.handleMessage(DispatchHelper.java:62)
at com.collaxa.cube.engine.dispatch.BaseScheduledWorker.process(BaseScheduledWorker.java:72)
at com.collaxa.cube.engine.bean.WorkerBean.onMessage(WorkerBean.java:86)
at com.evermind.server.ejb.MessageDrivenBeanInvocation.run(MessageDrivenBeanInvocation.java:123)
at com.evermind.server.ejb.MessageDrivenHome.onMessage(MessageDrivenHome.java:745)
at com.evermind.server.ejb.MessageDrivenHome.run(MessageDrivenHome.java:917)
at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:186)
at java.lang.Thread.run(Thread.java:534)
Caused by: java.lang.NumberFormatException: null
at java.lang.Integer.parseInt(Integer.java:436)
at java.lang.Integer.<init>(Integer.java:609)
at oracle.tip.adapter.db.sp.XSDParser.parseParameters(XSDParser.java:221)
at oracle.tip.adapter.db.sp.SPInteraction.executeStoredProcedure(SPInteraction.java:69)
at oracle.tip.adapter.db.DBInteraction.executeStoredProcedure(DBInteraction.java:421)
... 27 more
java.lang.NumberFormatException: null
at java.lang.Integer.parseInt(Integer.java:436)
at java.lang.Integer.<init>(Integer.java:609)
at oracle.tip.adapter.db.sp.XSDParser.parseParameters(XSDParser.java:221)
at oracle.tip.adapter.db.sp.SPInteraction.executeStoredProcedure(SPInteraction.java:69)
at oracle.tip.adapter.db.DBInteraction.executeStoredProcedure(DBInteraction.java:421)
at oracle.tip.adapter.db.DBInteraction.execute(DBInteraction.java:140)
at oracle.tip.adapter.fw.wsif.jca.WSIFOperation_JCA.executeRequestResponseOperation(WSIFOperation_JCA.java:395)
at com.collaxa.cube.ws.WSIFInvocationHandler.invoke(WSIFInvocationHandler.java:356)
at com.collaxa.cube.ws.WSInvocationManager.invoke(WSInvocationManager.java:288)
at com.collaxa.cube.ws.WSInvocationManager.invoke(WSInvocationManager.java:134)
at com.collaxa.cube.engine.ext.wmp.BPELInvokeWMP.__invoke(BPELInvokeWMP.java:541)
at com.collaxa.cube.engine.ext.wmp.BPELInvokeWMP.__executeStatements(BPELInvokeWMP.java:284)
at com.collaxa.cube.engine.ext.wmp.BPELActivityWMP.perform(BPELActivityWMP.java:178)
at com.collaxa.cube.engine.CubeEngine.performActivity(CubeEngine.java:3438)
at com.collaxa.cube.engine.CubeEngine.handleWorkItem(CubeEngine.java:1818)
at com.collaxa.cube.engine.dispatch.message.instance.PerformMessageHandler.handleLocal(PerformMessageHandler.java:75)
at com.collaxa.cube.engine.dispatch.DispatchHelper.handleLocalMessage(DispatchHelper.java:85)
at com.collaxa.cube.engine.dispatch.DispatchHelper.sendMemory(DispatchHelper.java:138)
at com.collaxa.cube.engine.CubeEngine.endRequest(CubeEngine.java:5522)
at com.collaxa.cube.engine.CubeEngine.createAndInvoke(CubeEngine.java:1221)
at com.collaxa.cube.engine.delivery.DeliveryService.handleInvoke(DeliveryService.java:480)
at com.collaxa.cube.engine.bean.DeliveryBean.handleInvoke(DeliveryBean.java:307)
at IDeliveryLocalBean_StatelessSessionBeanWrapper16.handleInvoke(IDeliveryLocalBean_StatelessSessionBeanWrapper16.java:1791)
at com.collaxa.cube.engine.dispatch.message.invoke.InvokeInstanceMessageHandler.handle(InvokeInstanceMessageHandler.java:36)
at com.collaxa.cube.engine.dispatch.DispatchHelper.handleMessage(DispatchHelper.java:62)
at com.collaxa.cube.engine.dispatch.BaseScheduledWorker.process(BaseScheduledWorker.java:72)
at com.collaxa.cube.engine.bean.WorkerBean.onMessage(WorkerBean.java:86)
at com.evermind.server.ejb.MessageDrivenBeanInvocation.run(MessageDrivenBeanInvocation.java:123)
at com.evermind.server.ejb.MessageDrivenHome.onMessage(MessageDrivenHome.java:745)
at com.evermind.server.ejb.MessageDrivenHome.run(MessageDrivenHome.java:917)
at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:186)
at java.lang.Thread.run(Thread.java:534)
<2004-12-01 10:48:52,300> <DEBUG> <default.collaxa.cube.ws> <WSIFInvocationHandler::invoke> Fault happenned
ORABPEL-11813
Encountered an unexpected exception while trying to execute the interaction.
An unexpected exception occurred while trying to execute the interaction for invoking the API.
Analyze and correct the error if possible. Contact oracle support if error is not fixable.
at oracle.tip.adapter.db.DBInteraction.executeStoredProcedure(DBInteraction.java:429)
at oracle.tip.adapter.db.DBInteraction.execute(DBInteraction.java:140)
at oracle.tip.adapter.fw.wsif.jca.WSIFOperation_JCA.executeRequestResponseOperation(WSIFOperation_JCA.java:395)
at com.collaxa.cube.ws.WSIFInvocationHandler.invoke(WSIFInvocationHandler.java:356)
at com.collaxa.cube.ws.WSInvocationManager.invoke(WSInvocationManager.java:288)
at com.collaxa.cube.ws.WSInvocationManager.invoke(WSInvocationManager.java:134)
at com.collaxa.cube.engine.ext.wmp.BPELInvokeWMP.__invoke(BPELInvokeWMP.java:541)
at com.collaxa.cube.engine.ext.wmp.BPELInvokeWMP.__executeStatements(BPELInvokeWMP.java:284)
at com.collaxa.cube.engine.ext.wmp.BPELActivityWMP.perform(BPELActivityWMP.java:178)
at com.collaxa.cube.engine.CubeEngine.performActivity(CubeEngine.java:3438)
at com.collaxa.cube.engine.CubeEngine.handleWorkItem(CubeEngine.java:1818)
at com.collaxa.cube.engine.dispatch.message.instance.PerformMessageHandler.handleLocal(PerformMessageHandler.java:75)
at com.collaxa.cube.engine.dispatch.DispatchHelper.handleLocalMessage(DispatchHelper.java:85)
at com.collaxa.cube.engine.dispatch.DispatchHelper.sendMemory(DispatchHelper.java:138)
at com.collaxa.cube.engine.CubeEngine.endRequest(CubeEngine.java:5522)
at com.collaxa.cube.engine.CubeEngine.createAndInvoke(CubeEngine.java:1221)
at com.collaxa.cube.engine.delivery.DeliveryService.handleInvoke(DeliveryService.java:480)
at com.collaxa.cube.engine.bean.DeliveryBean.handleInvoke(DeliveryBean.java:307)
at IDeliveryLocalBean_StatelessSessionBeanWrapper16.handleInvoke(IDeliveryLocalBean_StatelessSessionBeanWrapper16.java:1791)
at com.collaxa.cube.engine.dispatch.message.invoke.InvokeInstanceMessageHandler.handle(InvokeInstanceMessageHandler.java:36)
at com.collaxa.cube.engine.dispatch.DispatchHelper.handleMessage(DispatchHelper.java:62)
at com.collaxa.cube.engine.dispatch.BaseScheduledWorker.process(BaseScheduledWorker.java:72)
at com.collaxa.cube.engine.bean.WorkerBean.onMessage(WorkerBean.java:86)
at com.evermind.server.ejb.MessageDrivenBeanInvocation.run(MessageDrivenBeanInvocation.java:123)
at com.evermind.server.ejb.MessageDrivenHome.onMessage(MessageDrivenHome.java:745)
at com.evermind.server.ejb.MessageDrivenHome.run(MessageDrivenHome.java:917)
at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:186)
at java.lang.Thread.run(Thread.java:534)
Caused by: java.lang.NumberFormatException: null
at java.lang.Integer.parseInt(Integer.java:436)
at java.lang.Integer.<init>(Integer.java:609)
at oracle.tip.adapter.db.sp.XSDParser.parseParameters(XSDParser.java:221)
at oracle.tip.adapter.db.sp.SPInteraction.executeStoredProcedure(SPInteraction.java:69)
at oracle.tip.adapter.db.DBInteraction.executeStoredProcedure(DBInteraction.java:421)
... 27 more
<2004-12-01 10:48:52,302> <DEBUG> <default.collaxa.cube.ws> <BPELInvokeWMP::__invoke> Caught RemoteException
orabpel.apache.wsif.WSIFException: oracle.tip.adapter.fw.wsif.jca.WSIFOperation_JCA@788a7bhttp://orcldemo.localdomain:9700/orabpel/default/StoredProcedure/StoredProcedureOutbound.wsdl[CataLog_ptt::CataLog(null)] : Could not invoke 'CataLog' due to: Encountered an unexpected exception while trying to execute the interaction.
An unexpected exception occurred while trying to execute the interaction for invoking the API.
Analyze and correct the error if possible. Contact oracle support if error is not fixable.
; nested exception is:
ORABPEL-11813
Encountered an unexpected exception while trying to execute the interaction.
An unexpected exception occurred while trying to execute the interaction for invoking the API.
Analyze and correct the error if possible. Contact oracle support if error is not fixable.
at oracle.tip.adapter.fw.wsif.jca.WSIFOperation_JCA.executeRequestResponseOperation(WSIFOperation_JCA.java:464)
at com.collaxa.cube.ws.WSIFInvocationHandler.invoke(WSIFInvocationHandler.java:356)
at com.collaxa.cube.ws.WSInvocationManager.invoke(WSInvocationManager.java:288)
at com.collaxa.cube.ws.WSInvocationManager.invoke(WSInvocationManager.java:134)
at com.collaxa.cube.engine.ext.wmp.BPELInvokeWMP.__invoke(BPELInvokeWMP.java:541)
at com.collaxa.cube.engine.ext.wmp.BPELInvokeWMP.__executeStatements(BPELInvokeWMP.java:284)
at com.collaxa.cube.engine.ext.wmp.BPELActivityWMP.perform(BPELActivityWMP.java:178)
at com.collaxa.cube.engine.CubeEngine.performActivity(CubeEngine.java:3438)
at com.collaxa.cube.engine.CubeEngine.handleWorkItem(CubeEngine.java:1818)
at com.collaxa.cube.engine.dispatch.message.instance.PerformMessageHandler.handleLocal(PerformMessageHandler.java:75)
at com.collaxa.cube.engine.dispatch.DispatchHelper.handleLocalMessage(DispatchHelper.java:85)
at com.collaxa.cube.engine.dispatch.DispatchHelper.sendMemory(DispatchHelper.java:138)
at com.collaxa.cube.engine.CubeEngine.endRequest(CubeEngine.java:5522)
at com.collaxa.cube.engine.CubeEngine.createAndInvoke(CubeEngine.java:1221)
at com.collaxa.cube.engine.delivery.DeliveryService.handleInvoke(DeliveryService.java:480)
at com.collaxa.cube.engine.bean.DeliveryBean.handleInvoke(DeliveryBean.java:307)
at IDeliveryLocalBean_StatelessSessionBeanWrapper16.handleInvoke(IDeliveryLocalBean_StatelessSessionBeanWrapper16.java:1791)
at com.collaxa.cube.engine.dispatch.message.invoke.InvokeInstanceMessageHandler.handle(InvokeInstanceMessageHandler.java:36)
at com.collaxa.cube.engine.dispatch.DispatchHelper.handleMessage(DispatchHelper.java:62)
at com.collaxa.cube.engine.dispatch.BaseScheduledWorker.process(BaseScheduledWorker.java:72)
at com.collaxa.cube.engine.bean.WorkerBean.onMessage(WorkerBean.java:86)
at com.evermind.server.ejb.MessageDrivenBeanInvocation.run(MessageDrivenBeanInvocation.java:123)
at com.evermind.server.ejb.MessageDrivenHome.onMessage(MessageDrivenHome.java:745)
at com.evermind.server.ejb.MessageDrivenHome.run(MessageDrivenHome.java:917)
at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:186)
at java.lang.Thread.run(Thread.java:534)
Caused by: ORABPEL-11813
Encountered an unexpected exception while trying to execute the interaction.
An unexpected exception occurred while trying to execute the interaction for invoking the API.
Analyze and correct the error if possible. Contact oracle support if error is not fixable.
at oracle.tip.adapter.db.DBInteraction.executeStoredProcedure(DBInteraction.java:429)
at oracle.tip.adapter.db.DBInteraction.execute(DBInteraction.java:140)
at oracle.tip.adapter.fw.wsif.jca.WSIFOperation_JCA.executeRequestResponseOperation(WSIFOperation_JCA.java:395)
... 25 more
Caused by: java.lang.NumberFormatException: null
at java.lang.Integer.parseInt(Integer.java:436)
at java.lang.Integer.<init>(Integer.java:609)
at oracle.tip.adapter.db.sp.XSDParser.parseParameters(XSDParser.java:221)
at oracle.tip.adapter.db.sp.SPInteraction.executeStoredProcedure(SPInteraction.java:69)
at oracle.tip.adapter.db.DBInteraction.executeStoredProcedure(DBInteraction.java:421)
... 27 more -
Problem with calling AQ JMS Adapter with Asynchronous BPEL Process
I have a AQ JMS Adapter and i'm invoking the adapter in my BPEL process.
I'm passing an xml as payload to AQ JMS adapter. When i post the xml in the BPEL Control, i'm getting the follwoing message:
"Cannot find the specified instance". I have tried 3-4 times but getting same message all the time.
However, i'm able to publish xml to JMS Topic with synchronous BPEL process.
I want to use asynchronous BPLE process.
Please let me know if there is a way to overcome this issue.
Thanks in advance.
Thanx in Advance.I am experiencing the exact same issue while configuring for Tibco EMS!!!
I have also checked the oc4j-xa.xml file etc and I am also unable to find any guidance on the steps required from XML config files through to adapter wizard entries! -
Why Java RMI client failed to invoking a mid-tier BPEL process?
I have followed the sample code (102.InvokingProcess/rmi). I have problem invoking the same process from the mid-tier server. Here is what I got:
[java] {java.naming.provider.url=ormi://btl-larcis5:12401/orabpel, java.nam
ing.factory.initial=com.evermind.server.rmi.RMIInitialContextFactory, orabpel.pl
atform=oc4j_10g, java.naming.security.principal=admin, java.naming.security.cred
entials=welcome}
[java] java.lang.Exception: Failed to create "ejb/collaxa/system/DomainMana
gerBean" bean; exception reported is: "javax.naming.NamingException: Lookup error: javax.naming.AuthenticationException: No such domain/application: orabpel; nested exception is:
[java] javax.naming.AuthenticationException: No such domain/application: orabpel [Root exception is javax.naming.AuthenticationException: No such domain/application: orabpel]
Here is my context.properties :
orabpel.platform=oc4j_10g
java.naming.factory.initial=com.evermind.server.rmi.RMIInitialContextFactory
java.naming.provider.url=ormi://my-mid-tier:12401/orabpel
java.naming.security.principal=admin
java.naming.security.credentials=welcome
I know the problem is in the provider url. If I change the java.naming.provider.url =ormi://my-pc /orabpel then it works fine. Has anyone gotten the sample code working from a mid-tier installation? My mid-tier is on version 10.1.2.02. Port 12401 is the default port number for RMI.I figured it out! The reason it did not work was the port number in the provider URL was wrong. It should be 12402. It toke me a little while to figure it. Should this be documented somewhere?
-
Calling a BPEL process from java
Hi all,
I have created a java code with RMI call to a BPEL process. I have published this java class as WebService.
I have deployed the WS on server. When I am calling WS its not invoking the BPEL Process.But when I am running the java code directly I am able to get the required output . What could be the problem?
I am using SOA server 10.1.3.4
I have imported following jars:
J2EE.jar, JAX-RPC Client.jar, xmlparserv2.jar, orawsdl.jar, oracle_http_client.jar, orabpel-thirdparty.jar, orabpel-common.jar, orabpel.jar, orabpel-boot.jar, oc4j-internal.jar, oc4jclient.jar, oc4j.jarHi,
Are you running the webservice on the same app-server as BPEL PM?
If so, what app-server do you use? According to the jar files you mention I assume Oracle AS 10g. Do you have your WS in the Home or the OC4J_SOA container?
Make sure that the jars you mention are available to the container you run your WS in.
Most of the libraries you mention are AS libraries. What I usually do is split my Webservices in two projects. One is a plain java project that does the job (in your case calling BPEL with the proper variables) en one J2EE project that implements the webservice part and calls the plain java project. The plain-java-project only gets the libraries it really needs. So no J2EE libs for example. In your case, probably only orabpel.jar and maybe orabpel-common and orabpel-boot.jar is needed. And if you're doing xml, then the xmlparserv2.jar. The jars you need for the plain-java-project are the only jars you need to deliver with the webservice. You can create shared libraries for it or add them to the lib folder of the AS. The libraries the J2EE project needs are appserver libraries that you don't need to deliver.
I find it best practice to minimize the libraries you deliver to only those really needed, without the J2EE libs. Every other library you deliver out of "Easyness" is mistify your view on problems.
You can try to add these libraries as a shared library. Or add them in one of the deployment steps. Or if these two don't work, try to ship them in your war-file.
Hope this helps.
If you need more help, may be you should dig up some errors. Look in to the servers logs, for example the logs in <Soa_home>/opmn/logs. Especially the one of the container your webservice is running in.
Regards,
Martien -
ESB Call to BPEL contains the Version of BPEL Process
Hi,
I'm creating a ESB Routing Service to call a BPEL Process.
Although I do not pout the version of the BPEL process on the WSDL that i give to the ESB Routing Service it always call the version to what it was developed, even thought i created a new version of the BPEL process and mark it as default.
What can i do to make that ESB Routing service call the default version of the BPEL process?
Thanks,
AlexIf i select the wsdl of the bpel, it would normally use an url like :
<host>/orabpel/default/BPELProcess2/2.0/BPELProcess2?wsdl
if i mark 2.0 as default and use an url like :
<host>/orabpel/default/BPELProcess2/BPELProcess2?wsdl
(so skip the version notification), it just uses the default-marked wsdl (version 2.0) in this case. -
BPEL process instances remain in-flight
Hi
I've got a BPEL process (GetUpdates) that calls a couple of other asynchronous BPEL processes (CommitPerson, CommitAddress etc) all of which are deployed on the same SOA server.
Although most of the processes complete, quite a few instances of the GetUpdates process just sit in an Active state. The BPEL console shows GetUpdates has made a call to another process (for example CommitAddress) and it is apparently waiting for a response. However when I examine the cube_instance table in the dehydration store I can only find 1 instance relating to the particular process. Is that correct?
If I then try to re-run these particular failed updates (by modifying the sequencing table that GetUpdates polls) the processes complete without any issue (and records exist in the cube_instance table for each of the processes that have been called as well).
There can be a large number of requests being processed so could this problem be due to the server being under too much load, with the invoke being lost in the ether somewhere?!?
Is there any documentation that explains the workings of the dehydration store or the BPEL server itself? Also what log files I should be looking at? (I'd really like to understand what's happening under the covers!!!)
We're currently only using 10.1.3.1 SOA Suite so we should probably upgrade to 10.1.3.3 to see if that fixes anything.
Any help or advice in the meantime would be great.
Thanks
RobinHi
Just thought I'd update this posting with my findings ....
I think that the reason the instances remained inflight was simply because they were making calls to synchronous processes that were timing out.
The default timeout setting for synchronous processes is from what I've read 45 seconds. The process instances that remained inflight were calling other (asynchronous) BPEL processes, that in turn called synchronous E-Business suite APIs that were timing out.
I managed to simulate the above some time ago with dummy BPEL processes, however I have only just now (after several months of dealing with Oracle Support!) managed to resolve the E-Business suite problem that was causing the synchronous process to timeout.
Anyway now that is resolved, we no longer get the large number of process instances remaining inflight ... and the updates are now flying along on the server!!
Therefore the issue was a very simple one - timeout of synchronous processes. Unfortunately it wasn't all that obvious that it was happening in the first place(!) ... and it took some time to trace the actual culprit ... and even longer to find a solution (which we had to come up with ourselves ... without much help from support!) ... hence the amount of time that has passed from me creating this message and replying to it!
Anyway I hope this post may help others in case they stumble upon a similar issue. -
HowTo get the callback from an asynchronous BPEL process to an ESB?
Hi,
I have deployed an asynchronous BPEL-process which is called from an ESB. So far no problems. But I want to receive the callboack fromt this BPEL process on the ESB, too.
How is this possible?
Note: I have created the BPEL-Process before I created the ESB. So I cannot add the ESB as a partner link in the BPEL Process. Or is this the only way?
Message was edited by:
user636134Hi,
I have deployed an asynchronous BPEL-process which is called from an ESB. So far no problems. But I want to receive the callboack fromt this BPEL process on the ESB, too.
How is this possible?
Note: I have created the BPEL-Process before I created the ESB. So I cannot add the ESB as a partner link in the BPEL Process. Or is this the only way?
Message was edited by:
user636134 -
How-to prioritize BPEL processes in BPEL PM 10.1.3.4
Hi there,
I would like to control the priority of my BPEL processes (in 10.1.3.4). In the documentation I read that this can be done via the embedded java method setPriority(). However, I am not sure if I should call the method from the appropriate BPEL process or if it should be done from the calling (higher-level) process.
Are there any examples available?
Thanks a lot, DaniloHi Marc,
thanks for your answer! What are the reasons why you wouldn't recommend to use it?
The idea is to simply process some instances in a more preffered way. Imagine you have a Flow-Activity and certain sub-processes will be called inside. Depending on the content it is necessary to execute the process in branch A before the process in branch B or vice versa (simplified example).
I assume there are no documents with some explanations about alternative methods...
Apart from this, if I use the embedded setPrio, where should I position it?
a) Within the calling process (I would guess so) or
b) Within the process that should be prioritized
Danilo -
BPM Receive Activity not FIFO ?
Hi,
11.1.1.7
We have a receive activity in a Singleton BPM process (not a great pattern, recognised!). Prior to the singleton receive activity being reached there may be 100's or 1000's of calls made to it. We have noticed that these are not processed in order.
Is this expected ?
Is there a way of making the activity receive requests in a FIFO fashion ?
Any help much appreciated.
cheers
TonyWell it is now solved...
I still don't know what was causing the issue, however when upgrading to weblogic 10.3.6 and soa 11.1.1.6 the issue was gone.
Probably was some installed patch or something on the server that was causing such behaviour. -
Unable to send a SOAP attachment(pdf) in a BPEL process
Dear Forum,
I have a requirement to attach a pdf and send it as part of a BPEL process response. Following are the details,
1) I have a webservice which does the logic of building the pdf and returns it as a SOAP attachment. I have tested this service through SOAP UI and it works fine.
2) I have a BPEL process which invokes the above webservice and returns the received pdf as a SOAP attachment.
3) Since BPEL designer doesn't directly support the MIME attachments, I have modified the WSDL related to BPEL process to include MIME parts. Followed the steps as mentioned in the SOA suite documentation - http://docs.oracle.com/cd/B14099_19/integrate.1012/b14448/manipdoc.htm#BABDEEEB
4) I have tested my bpel service through SOAP UI tool (cannot test it in 'em' console since my service has mime parts) but unable to receive the pdf attachment. BPEL process is throwing the following exception,
<Mar 26, 2012 5:21:07 PM EDT> <Warning> <oracle.adfinternal.view.faces.renderkit
.rich.TreeRendererUtils> <BEA-000000> <Context menu child is not a RichMenu>
<Mar 26, 2012 5:22:19 PM EDT> <Error> <oracle.soa.bpel.engine.ws> <BEA-000000> <
got RuntimeException
java.lang.NullPointerException
at oracle.integration.platform.attchmnt.AttachmentManagerImpl.encodeProp
erties(AttachmentManagerImpl.java:569)
at oracle.integration.platform.attchmnt.AttachmentManagerImpl.insertAtta
chment(AttachmentManagerImpl.java:483)
at oracle.integration.platform.attchmnt.AttachmentManagerImpl.storeAttac
hment(AttachmentManagerImpl.java:189)
at oracle.integration.platform.attchmnt.AttachmentManagerImpl.storeAttac
hment(AttachmentManagerImpl.java:144)
From the SOAP UI response(error message), I found that 'Content-Type' for this request is coming as 'text/xml' rather than 'mimemultipartrelated'. Is it not possible to send pdf attachments through BPEL? Please provide your inputs to resolve this issue. I am stuck up with this issue for a while now.Hi Vamsee,
In my case pdf is returned by a webservice, not from any physical location. The example given there shows attaching a pdf file from physical location. But I will get the pdf as part of another webservice response. So I am assigning the attachment to a bpel variable after getting the webservice response. This is where my bpel process is throwing an exception mentioned above.
Regards,
Satya. -
Calling a BPEL process from EDN
Hi all,
I'm in trouble to try to communicate two BPEL process via EDN (Event Delivery Network).
The example is quite simple:
TestProcess is a BPEL process which exposes a SOAP service, performs some tasks and wait for an event through a receive activity ( it acts as event subscriber).
TestProcessEvent is a BPEL process which exposes a second SOAP service that publish the event to EDN ( it acts as event publisher).
The test I performed is:
start an instance of TestProcess and verify it is on running state, waiting for the event.
start an instance of TestProcessEvent and verify if the event is delivered and then verify the instance of TestProcess resumes.
Unfortunately TestProcessEvent finished but the event isn't propagated to TestProcess that remains running.
I have also tried using correllation, but in this case the error is:
ORABPEL-03812
java.security.PrivilegedActionException: oracle.fabric.common.FabricInvocationException
Cannot find property alias.
Cannot find the property alias "{....}"".
Please check your BPEL/WSDL source to make sure that property alias "{...}" has been defined.
I suspect that the first issue (event is not propagated by BPEL process) is related to the problem with correlation.
Any idea?
Thanks in advance,
Daniel.Hi,
Are you running the webservice on the same app-server as BPEL PM?
If so, what app-server do you use? According to the jar files you mention I assume Oracle AS 10g. Do you have your WS in the Home or the OC4J_SOA container?
Make sure that the jars you mention are available to the container you run your WS in.
Most of the libraries you mention are AS libraries. What I usually do is split my Webservices in two projects. One is a plain java project that does the job (in your case calling BPEL with the proper variables) en one J2EE project that implements the webservice part and calls the plain java project. The plain-java-project only gets the libraries it really needs. So no J2EE libs for example. In your case, probably only orabpel.jar and maybe orabpel-common and orabpel-boot.jar is needed. And if you're doing xml, then the xmlparserv2.jar. The jars you need for the plain-java-project are the only jars you need to deliver with the webservice. You can create shared libraries for it or add them to the lib folder of the AS. The libraries the J2EE project needs are appserver libraries that you don't need to deliver.
I find it best practice to minimize the libraries you deliver to only those really needed, without the J2EE libs. Every other library you deliver out of "Easyness" is mistify your view on problems.
You can try to add these libraries as a shared library. Or add them in one of the deployment steps. Or if these two don't work, try to ship them in your war-file.
Hope this helps.
If you need more help, may be you should dig up some errors. Look in to the servers logs, for example the logs in <Soa_home>/opmn/logs. Especially the one of the container your webservice is running in.
Regards,
Martien -
Any API to get handle to Outbound BPEL process endpoint activation?
Hi,
we are developing both inbound and outbound BPEL processes using a custom JCA 1.5 based adapter. For the inbound BPEL process deployment/undeployment, we have the ResourceAdapter's endpointActivate() endpointDeactivate() methods called in and so we can post process, like clean up endpoints when these methods get called. Is there somethign simillar that we can use as an API to get a handle to the outbound process endpoints deactivate/activate, so that we can clean up these too, or does the oracle adapter framework internally clean these up?
Also even though we undeploy all processes before stopping the adapter (from the bpel console), after that if we redeploy the adapter rar, from then on any new BPEL process deployment (through jdeveloper) always throws a "500 Internal Server Error". Only after restarting the SOA, then on any new deployments go through fine. This is a serious limitation for us.. Any idea why this is happening and how to resolve this?
Thanks
PramodhHi Pramodh,
That's a nice requirement.
The inbound (ActivationSpec) properties can only be set dynamically (typically via the BPEL console) if their values are bound via property values defined in bpel.xml for the particular JCA Activation Agent in question. This is fundamentally as per the JCA 1.5 design where EndpointActivation (which receives an instance of ActivationSpec) takes place when the BPEL process starts up, i.e. only once. More often than not the BPEL process will have to be bounced (Off/On) for ActivationSpec attribute changes to take effect (thereby allowing the JCA 1.5 inbound message endpoint to be restarted/reinitialized). Some adapters do look dynamically for changes to bpel.xml bound values (subscribed to via the adapter framework) and will react appropriately without the need for bumping the process (e.g. adjusting a timeout or retryCount or other secondary attribute which doesn't change the first order attributes of the endpoint, such as e.g. the database host name etc). An example of an activation property which requires the adapter to restart is the JMS adapter MessageSelector property.
Having said that, please try using the activation agent properties set in the outbound PL and see if that works!
Cheers
A
Maybe you are looking for
-
New GL - Goods Movements in only one ledger.
Hi all, we have a scenario where we have New GL active and use the leading ledger for IFRS and other ledger for local gap. For some material types, IFRS considers it as an inventory material but in local gaap it is consider an expense. And for a lega
-
When is XSQL 9.0.2A going to be released?
I need the <xsql:include-xml>select...</sql:include-xml> feature to render xml from clobs. As of right now it is rendering as "<element>...</element>" instead of "<element>...</element>" (something like that).
-
Hi, I am working on an press force monitoring application. Right not I am plotting diplacement vs. force. I am looking to create an upper and lower limit for this plot that can be x and y axis adjustable. It sounds easy enough but I'm racking my brai
-
EBS R12.2.4 Oracle Customer Online, profile UDA error "JBO-26010" UomExtAttr1
Hi, all In EBS R12.2.4, OCO define a UDA for profile, not display in profile page, show error page, has below error "JBO-26010: Invalid Entity Attribute Name "UomExtAttr1" ", any help is appreciate.
-
Task and resource management without HU and SU
Hi experts, I know that it is possible to use TRM with SU and without HU. Is it possibile to use TRM without HU and SU? Thanks in advance Regards M.