ESB calling BPEL service

Hello All.
We have created an ESB that includes a database partner link that reads new records then uses that data and calls a BPEL process.
We have a single server in development and clustered servers in test, qa and prod.
In dev, the ESB calls the BPEL process once as it should.
In the clustered environments, the ESB calls the BPEL process twice. In the ESB console there is only one instance of the ESB and in the BPEL console there are two.
Is this a bug in the software or is there a ESB/BPEL configuration that we might have missed?
Thanks in advance.

You need to implement the DB polling as a singleton service. What is happing is the activation agent is running on both nodes. You need to make it run on just one.
have a look at metalink note 746108.1
also the enterprise deployment guide provides pointers
http://download.oracle.com/docs/cd/E10291_01/core.1013/e10294/webapp.htm#sthref142
cheers
James

Similar Messages

ARS (Remedy) Call BPEL Service

I am trying to get Remedy to call a BPEL webservice. Using HelloWorld example. I am unable to parse the wsdl from there tool. Has anyone found a workaround to this? Maybe saving the wsdl local and editing the file.
Here is what a Remedy Web service looks like....
<?xml version="1.0" encoding="UTF-8" ?>
- <wsdl:definitions targetNamespace="urn:CC_Goodlink" xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:s="urn:CC_Goodlink" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
- <wsdl:types>
- <xsd:schema elementFormDefault="qualified" targetNamespace="urn:CC_Goodlink">
<xsd:element name="OpGetGoodlink" type="s:GetInputMap11" />
- <xsd:complexType name="GetInputMap11">
- <xsd:sequence>
<xsd:element name="Request_ID" type="xsd:string" />
</xsd:sequence>
</xsd:complexType>
<xsd:element name="OpGetGoodlinkResponse" type="s:GetOutputMap11" />
- <xsd:complexType name="GetOutputMap11">
- <xsd:sequence>
<xsd:element name="ChangeControlCategory" type="xsd:string" />
<xsd:element name="Request_ID" type="xsd:string" />
<xsd:element name="ResponsibleGroup" type="xsd:string" />
<xsd:element name="Short_Description" type="xsd:string" />
<xsd:element name="TypeOfChange" type="s:TypeOfChangeType" />
<xsd:element name="Status" type="s:StatusType" />
<xsd:element name="Changes_Planned" type="xsd:string" />
<xsd:element name="Start_Time" type="xsd:dateTime" />
<xsd:element name="Stop_Time" type="xsd:dateTime" />
<xsd:element name="Devices_Effected" type="xsd:string" />
<xsd:element name="Software_notes" type="xsd:string" />
<xsd:element name="Back_out_instructions" type="xsd:string" />
<xsd:element name="notes" type="xsd:string" />
</xsd:sequence>
</xsd:complexType>
- <xsd:simpleType name="TypeOfChangeType">
- <xsd:restriction base="xsd:string">
<xsd:enumeration value="Standard" />
<xsd:enumeration value="Informational" />
<xsd:enumeration value="Emergency" />
<xsd:enumeration value="Retrospective" />
</xsd:restriction>
</xsd:simpleType>
- <xsd:simpleType name="StatusType">
- <xsd:restriction base="xsd:string">
<xsd:enumeration value="New" />
<xsd:enumeration value="Requested" />
<xsd:enumeration value="Approved" />
<xsd:enumeration value="Change In Progress" />
<xsd:enumeration value="Rejected" />
<xsd:enumeration value="Completed" />
<xsd:enumeration value="Cancelled" />
<xsd:enumeration value="Re-Scheduling" />
<xsd:enumeration value="Backed-Out" />
</xsd:restriction>
</xsd:simpleType>
<xsd:element name="OpSetGoodlink" type="s:InputMapping" />
- <xsd:complexType name="InputMapping">
- <xsd:sequence>
<xsd:element name="Status" type="s:StatusType" />
<xsd:element name="Request_ID" type="xsd:string" />
</xsd:sequence>
</xsd:complexType>
<xsd:element name="OpSetGoodlinkResponse" type="s:OutputMapping" />
- <xsd:complexType name="OutputMapping">
- <xsd:sequence>
<xsd:element name="Status" type="s:StatusType" />
</xsd:sequence>
</xsd:complexType>
<xsd:element name="AuthenticationInfo" type="s:AuthenticationInfo" />
- <xsd:complexType name="AuthenticationInfo">
- <xsd:sequence>
<xsd:element name="userName" type="xsd:string" />
<xsd:element name="password" type="xsd:string" />
<xsd:element minOccurs="0" name="authentication" type="xsd:string" />
<xsd:element minOccurs="0" name="locale" type="xsd:string" />
<xsd:element minOccurs="0" name="timeZone" type="xsd:string" />
</xsd:sequence>
</xsd:complexType>
</xsd:schema>
</wsdl:types>
- <wsdl:message name="OpSetGoodlinkSoapOut">
<wsdl:part element="s:OpSetGoodlinkResponse" name="parameters" />
</wsdl:message>
- <wsdl:message name="ARAuthenticate">
<wsdl:part element="s:AuthenticationInfo" name="parameters" />
</wsdl:message>
- <wsdl:message name="OpGetGoodlinkSoapOut">
<wsdl:part element="s:OpGetGoodlinkResponse" name="parameters" />
</wsdl:message>
- <wsdl:message name="OpSetGoodlinkSoapIn">
<wsdl:part element="s:OpSetGoodlink" name="parameters" />
</wsdl:message>
- <wsdl:message name="OpGetGoodlinkSoapIn">
<wsdl:part element="s:OpGetGoodlink" name="parameters" />
</wsdl:message>
- <wsdl:portType name="CC_GoodlinkPortType">
- <wsdl:operation name="OpGetGoodlink">
<wsdl:input message="s:OpGetGoodlinkSoapIn" />
<wsdl:output message="s:OpGetGoodlinkSoapOut" />
</wsdl:operation>
- <wsdl:operation name="OpSetGoodlink">
<wsdl:input message="s:OpSetGoodlinkSoapIn" />
<wsdl:output message="s:OpSetGoodlinkSoapOut" />
</wsdl:operation>
</wsdl:portType>
- <wsdl:binding name="CC_GoodlinkSoapBinding" type="s:CC_GoodlinkPortType">
<soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http" />
- <wsdl:operation name="OpGetGoodlink">
<soap:operation soapAction="urn:CC_Goodlink/OpGetGoodlink" style="document" />
- <wsdl:input>
<soap:header message="s:ARAuthenticate" part="parameters" use="literal" />
<soap:body use="literal" />
</wsdl:input>
- <wsdl:output>
<soap:body use="literal" />
</wsdl:output>
</wsdl:operation>
- <wsdl:operation name="OpSetGoodlink">
<soap:operation soapAction="urn:CC_Goodlink/OpSetGoodlink" style="document" />
- <wsdl:input>
<soap:header message="s:ARAuthenticate" part="parameters" use="literal" />
<soap:body use="literal" />
</wsdl:input>
- <wsdl:output>
<soap:body use="literal" />
</wsdl:output>
</wsdl:operation>
</wsdl:binding>
- <wsdl:service name="CC_GoodlinkService">
- <wsdl:port binding="s:CC_GoodlinkSoapBinding" name="CC_GoodlinkSoap">
<soap:address location="http://remedy03.corp.tnsi.com/arsys/services/ARService?server=remedy03&webService=CC_Goodlink" />
</wsdl:port>
</wsdl:service>
</wsdl:definitions>

I am still unable to modify the wsdl directly to call from Remedy. I saw a previous post that suggest pulling out the prlnk statements, but alas no dice.

Calling BPEL service using axis client

Hi,
I have created and deployed simple BPEL process and i am trying to invoke this BPEL process using axis client.
deployed BPEL wsdl is as follows
<?xml version="1.0" encoding="UTF-8" ?>
- <definitions name="SimpleProcess" targetNamespace="http://xmlns.oracle.com/SimpleProcess" xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:tns="http://xmlns.oracle.com/SimpleProcess" xmlns:plnk="http://schemas.xmlsoap.org/ws/2003/05/partner-link/" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:client="http://xmlns.oracle.com/SimpleProcess">
- <types>
- <schema xmlns="http://www.w3.org/2001/XMLSchema">
<import namespace="http://xmlns.oracle.com/SimpleProcess" schemaLocation="SimpleProcess.xsd" />
</schema>
</types>
- <message name="SimpleProcessRequestMessage">
<part name="payload" element="tns:SimpleProcessProcessRequest" />
</message>
- <message name="SimpleProcessResponseMessage">
<part name="payload" element="tns:SimpleProcessProcessResponse" />
</message>
- <portType name="SimpleProcess">
- <operation name="process">
<input message="tns:SimpleProcessRequestMessage" />
<output message="tns:SimpleProcessResponseMessage" />
</operation>
</portType>
- <binding name="SimpleProcessBinding" type="tns:SimpleProcess">
<soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http" />
- <operation name="process">
<soap:operation style="document" soapAction="process" />
- <input>
<soap:body use="literal" />
</input>
- <output>
<soap:body use="literal" />
</output>
</operation>
</binding>
- <service name="SimpleProcess">
- <port name="SimpleProcessPort" binding="tns:SimpleProcessBinding">
<soap:address location="http://localhost:9700/orabpel/default/SimpleProcess/1.0" />
</port>
</service>
- <plnk:partnerLinkType name="SimpleProcess">
- <plnk:role name="SimpleProcessProvider">
<plnk:portType name="tns:SimpleProcess" />
</plnk:role>
</plnk:partnerLinkType>
</definitions>
and my soap client code is as follows
public static void main(String[] args) throws Exception {
     String endpoint =
     "http://ICON-OBCC.asiapacific.hpqcorp.net:9700/orabpel/default/SimpleProcess/1.0 ";
     Service service = new Service();
     Call call = (Call) service.createCall();
     call.setTargetEndpointAddress( new java.net.URL(endpoint) );
call.setOperationName(new QName("http://xmlns.oracle.com/TP", "process"));
String ret = (String) call.invoke( new Object[] { "FFF" } );
     System.out.println("Sent 'Hello!', got '" + ret + "'");
when i execute this i am getting follwoing error on BPEL console
Error - OWS-04005 an error occured for port BPEL_OC4j_SOAP_PROVIDER javx.xml.rpc.JAXRPCException java:lang:NullPointerException
Any indication for resolving this will be great help.
Thanks in advance
S

Hi,
I have created and deployed simple BPEL process and i am trying to invoke this BPEL process using axis client.
deployed BPEL wsdl is as follows
<?xml version="1.0" encoding="UTF-8" ?>
- <definitions name="SimpleProcess" targetNamespace="http://xmlns.oracle.com/SimpleProcess" xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:tns="http://xmlns.oracle.com/SimpleProcess" xmlns:plnk="http://schemas.xmlsoap.org/ws/2003/05/partner-link/" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:client="http://xmlns.oracle.com/SimpleProcess">
- <types>
- <schema xmlns="http://www.w3.org/2001/XMLSchema">
<import namespace="http://xmlns.oracle.com/SimpleProcess" schemaLocation="SimpleProcess.xsd" />
</schema>
</types>
- <message name="SimpleProcessRequestMessage">
<part name="payload" element="tns:SimpleProcessProcessRequest" />
</message>
- <message name="SimpleProcessResponseMessage">
<part name="payload" element="tns:SimpleProcessProcessResponse" />
</message>
- <portType name="SimpleProcess">
- <operation name="process">
<input message="tns:SimpleProcessRequestMessage" />
<output message="tns:SimpleProcessResponseMessage" />
</operation>
</portType>
- <binding name="SimpleProcessBinding" type="tns:SimpleProcess">
<soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http" />
- <operation name="process">
<soap:operation style="document" soapAction="process" />
- <input>
<soap:body use="literal" />
</input>
- <output>
<soap:body use="literal" />
</output>
</operation>
</binding>
- <service name="SimpleProcess">
- <port name="SimpleProcessPort" binding="tns:SimpleProcessBinding">
<soap:address location="http://localhost:9700/orabpel/default/SimpleProcess/1.0" />
</port>
</service>
- <plnk:partnerLinkType name="SimpleProcess">
- <plnk:role name="SimpleProcessProvider">
<plnk:portType name="tns:SimpleProcess" />
</plnk:role>
</plnk:partnerLinkType>
</definitions>
and my soap client code is as follows
public static void main(String[] args) throws Exception {
     String endpoint =
     "http://ICON-OBCC.asiapacific.hpqcorp.net:9700/orabpel/default/SimpleProcess/1.0 ";
     Service service = new Service();
     Call call = (Call) service.createCall();
     call.setTargetEndpointAddress( new java.net.URL(endpoint) );
call.setOperationName(new QName("http://xmlns.oracle.com/TP", "process"));
String ret = (String) call.invoke( new Object[] { "FFF" } );
     System.out.println("Sent 'Hello!', got '" + ret + "'");
when i execute this i am getting follwoing error on BPEL console
Error - OWS-04005 an error occured for port BPEL_OC4j_SOAP_PROVIDER javx.xml.rpc.JAXRPCException java:lang:NullPointerException
Any indication for resolving this will be great help.
Thanks in advance
S

ESB: Calling BPEL-Workflow

I am trying to initiate a BPEL-Workflow with ESB.
I am getting following error-message:
oracle.tip.esb.server.common.exceptions.BusinessEventFatalException: Eine unbehandelte Exception wurde im ESB-System ausgelöst. Es wurde folgende Exception gemeldet: "java.lang.Exception: Erstellen von "ejb/collaxa/system/DeliveryBean"-Bean nicht erfolgreich. Es wurde folgende Exception gemeldet: "javax.naming.NamingException: Lookup error: javax.naming.AuthenticationException: Not authorized; nested exception is:
     javax.naming.AuthenticationException: Not authorized [Root exception is javax.naming.AuthenticationException: Not authorized]
     at com.evermind.server.rmi.RMIClientContext.lookup(RMIClientContext.java:64)
     at javax.naming.InitialContext.lookup(InitialContext.java:351)
     at com.oracle.bpel.client.util.BeanRegistry.lookupDeliveryBean(BeanRegistry.java:279)
     at com.oracle.bpel.client.delivery.DeliveryService.getDeliveryBean(DeliveryService.java:250)
     at com.oracle.bpel.client.delivery.DeliveryService.request(DeliveryService.java:83)
     at com.oracle.bpel.client.delivery.DeliveryService.request(DeliveryService.java:67)
     at oracle.tip.esb.server.service.impl.bpel.BPELService.processBusinessEvent(Unknown Source)
     at oracle.tip.esb.server.dispatch.InitialEventDispatcher.dispatchNonRoutingService(Unknown Source)
     at oracle.tip.esb.server.dispatch.InitialEventDispatcher.dispatch(Unknown Source)
     at oracle.tip.esb.server.dispatch.BusinessEvent.raise(Unknown Source)
     at oracle.tip.esb.utils.EventUtils.raiseBusinessEvent(Unknown Source)
     at oracle.tip.esb.server.service.EsbRouterSubscription.onBusinessEvent(Unknown Source)
     at oracle.tip.esb.server.dispatch.EventDispatcher.executeSubscription(Unknown Source)
     at oracle.tip.esb.server.dispatch.InitialEventDispatcher.processSubscription(Unknown Source)
     at oracle.tip.esb.server.dispatch.InitialEventDispatcher.processSubscriptions(Unknown Source)
     at oracle.tip.esb.server.dispatch.EventDispatcher.dispatchRoutingService(Unknown Source)
     at oracle.tip.esb.server.dispatch.InitialEventDispatcher.dispatch(Unknown Source)
     at oracle.tip.esb.server.dispatch.BusinessEvent.raise(Unknown Source)
     at oracle.tip.esb.utils.EventUtils.raiseBusinessEvent(Unknown Source)
     at oracle.tip.esb.server.service.impl.inadapter.InboundAdapterService.raiseEvent(Unknown Source)
     at oracle.tip.esb.server.service.impl.inadapter.ESBListenerImpl.raiseEvent(Unknown Source)
     at oracle.tip.esb.server.service.impl.inadapter.ESBListenerImpl.processMessage(Unknown Source)
     at oracle.tip.esb.server.service.impl.inadapter.ESBListenerImpl.onMessage(Unknown Source)
     at oracle.tip.adapter.fw.jca.messageinflow.MessageEndpointImpl.onMessage(MessageEndpointImpl.java:279)
     at oracle.tip.adapter.db.InboundWork.onMessageImpl(InboundWork.java:1327)
     at oracle.tip.adapter.db.InboundWork.onMessage(InboundWork.java:1276)
     at oracle.tip.adapter.db.InboundWork.transactionalUnit(InboundWork.java:1230)
     at oracle.tip.adapter.db.InboundWork.runOnce(InboundWork.java:482)
     at oracle.tip.adapter.db.InboundWork.run(InboundWork.java:383)
     at oracle.tip.adapter.db.inbound.InboundWorkWrapper.run(InboundWorkWrapper.java:43)
     at oracle.j2ee.connector.work.WorkWrapper.runTargetWork(WorkWrapper.java:242)
     at oracle.j2ee.connector.work.WorkWrapper.doWork(WorkWrapper.java:215)
     at oracle.j2ee.connector.work.WorkWrapper.run(WorkWrapper.java:190)
     at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:814)
     at java.lang.Thread.run(Thread.java:595)
Caused by: javax.naming.AuthenticationException: Not authorized
     at oracle.oc4j.rmi.ClientRmiTransport.connectToServer(ClientRmiTransport.java:99)
     at oracle.oc4j.rmi.ClientSocketRmiTransport.connectToServer(ClientSocketRmiTransport.java:68)
     at com.evermind.server.rmi.RMIClientConnection.connect(RMIClientConnection.java:609)
     at com.evermind.server.rmi.RMIClientConnection.sendLookupRequest(RMIClientConnection.java:153)
     at com.evermind.server.rmi.RMIClientConnection.lookup(RMIClientConnection.java:137)
     at com.evermind.server.rmi.RMIClient.lookup(RMIClient.java:251)
     at com.evermind
Can anybody help, how to set the right permissions?

IMHO you did not solve your first problem. Because in first case you chose directly from routing service as target operation your BPEL process operation. And ESB wanted to execute that though RMI. Which has transaction support and is also faster. But your credentials were invalid. Therefore you got that exception.
After that you decided to use SOAP HTTP protocol, which is not transaction enabled and is slower :-(
In case you would like to use RMI, you have to change in your SOA Suite in this file:
<orahome>/bpel/utilities/ant-orabpel.properties
credentials for oc4jadmin user. After you update that, restart server.
And then it should work.

ESB calling BPEL: failed to handle message error

Hi all,
I'm trying to invoke a BPEL process from an ESB process but I'm getting the following error:
<2007-03-21 12:38:26,458> <ERROR> <default.collaxa.cube.engine.dispatch> <DispatchHelper::handleMessage> failed to handle message
javax.ejb.EJBException: An exception occurred during transaction completion: ; nested exception is: javax.transaction.RollbackException
javax.transaction.RollbackException
     at com.evermind.server.ApplicationServerTransaction.checkForRollbackOnlyWhileInCommit(ApplicationServerTransaction.java:582)
     at com.evermind.server.ApplicationServerTransaction.doCommit(ApplicationServerTransaction.java:244)
     at com.evermind.server.ApplicationServerTransaction.commit(ApplicationServerTransaction.java:130)
     at com.evermind.server.ApplicationServerTransactionManager.commit(ApplicationServerTransactionManager.java:433)
     at com.evermind.server.ejb.EJBTransactionManager.end(EJBTransactionManager.java:132)
     at com.evermind.server.ejb.interceptor.system.TxRequiredInterceptor.invoke(TxRequiredInterceptor.java:57)
     at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
     at com.evermind.server.ejb.interceptor.system.DMSInterceptor.invoke(DMSInterceptor.java:52)
     at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
     at com.evermind.server.ejb.InvocationContextPool.invoke(InvocationContextPool.java:55)
     at com.evermind.server.ejb.StatelessSessionEJBObject.OC4J_invokeMethod(StatelessSessionEJBObject.java:87)
     at CubeDeliveryBean_LocalProxy_4bin6i8.handleInvoke(Unknown Source)
     at com.collaxa.cube.engine.dispatch.message.invoke.InvokeInstanceMessageHandler.handle(InvokeInstanceMessageHandler.java:37)
     at com.collaxa.cube.engine.dispatch.DispatchHelper.handleMessage(DispatchHelper.java:138)
     at com.collaxa.cube.engine.dispatch.BaseScheduledWorker.process(BaseScheduledWorker.java:70)
     at com.collaxa.cube.engine.ejb.impl.WorkerBean.onMessage(WorkerBean.java:86)
     at sun.reflect.GeneratedMethodAccessor66.invoke(Unknown Source)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:585)
     at com.evermind.server.ejb.interceptor.joinpoint.EJBJoinPointImpl.invoke(EJBJoinPointImpl.java:35)
     at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
     at com.evermind.server.ejb.interceptor.system.DMSInterceptor.invoke(DMSInterceptor.java:52)
     at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
     at com.evermind.server.ejb.interceptor.system.SetContextActionInterceptor.invoke(SetContextActionInterceptor.java:44)
     at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
     at com.evermind.server.ejb.InvocationContextPool.invoke(InvocationContextPool.java:55)
     at oracle.j2ee.connector.messageinflow.MessageEndpointImpl.OC4J_invokeMethod(MessageEndpointImpl.java:297)
     at WorkerBean_EndPointProxy_4bin6i8.onMessage(Unknown Source)
     at oracle.j2ee.ra.jms.generic.WorkConsumer.run(WorkConsumer.java:266)
     at oracle.j2ee.connector.work.WorkWrapper.runTargetWork(WorkWrapper.java:242)
     at oracle.j2ee.connector.work.WorkWrapper.doWork(WorkWrapper.java:215)
     at oracle.j2ee.connector.work.WorkWrapper.run(WorkWrapper.java:190)
     at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:814)
     at java.lang.Thread.run(Thread.java:595)
javax.ejb.EJBException: An exception occurred during transaction completion: ; nested exception is: javax.transaction.RollbackException
     at com.evermind.server.ejb.EJBUtils.createEJBException(EJBUtils.java:365)
     at com.evermind.server.ejb.EJBTransactionManager.end(EJBTransactionManager.java:139)
     at com.evermind.server.ejb.interceptor.system.TxRequiredInterceptor.invoke(TxRequiredInterceptor.java:57)
     at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
     at com.evermind.server.ejb.interceptor.system.DMSInterceptor.invoke(DMSInterceptor.java:52)
     at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
     at com.evermind.server.ejb.InvocationContextPool.invoke(InvocationContextPool.java:55)
     at com.evermind.server.ejb.StatelessSessionEJBObject.OC4J_invokeMethod(StatelessSessionEJBObject.java:87)
     at CubeDeliveryBean_LocalProxy_4bin6i8.handleInvoke(Unknown Source)
     at com.collaxa.cube.engine.dispatch.message.invoke.InvokeInstanceMessageHandler.handle(InvokeInstanceMessageHandler.java:37)
     at com.collaxa.cube.engine.dispatch.DispatchHelper.handleMessage(DispatchHelper.java:138)
     at com.collaxa.cube.engine.dispatch.BaseScheduledWorker.process(BaseScheduledWorker.java:70)
     at com.collaxa.cube.engine.ejb.impl.WorkerBean.onMessage(WorkerBean.java:86)
     at sun.reflect.GeneratedMethodAccessor66.invoke(Unknown Source)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:585)
     at com.evermind.server.ejb.interceptor.joinpoint.EJBJoinPointImpl.invoke(EJBJoinPointImpl.java:35)
     at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
     at com.evermind.server.ejb.interceptor.system.DMSInterceptor.invoke(DMSInterceptor.java:52)
     at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
     at com.evermind.server.ejb.interceptor.system.SetContextActionInterceptor.invoke(SetContextActionInterceptor.java:44)
     at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
     at com.evermind.server.ejb.InvocationContextPool.invoke(InvocationContextPool.java:55)
     at oracle.j2ee.connector.messageinflow.MessageEndpointImpl.OC4J_invokeMethod(MessageEndpointImpl.java:297)
     at WorkerBean_EndPointProxy_4bin6i8.onMessage(Unknown Source)
     at oracle.j2ee.ra.jms.generic.WorkConsumer.run(WorkConsumer.java:266)
     at oracle.j2ee.connector.work.WorkWrapper.runTargetWork(WorkWrapper.java:242)
     at oracle.j2ee.connector.work.WorkWrapper.doWork(WorkWrapper.java:215)
     at oracle.j2ee.connector.work.WorkWrapper.run(WorkWrapper.java:190)
     at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:814)
     at java.lang.Thread.run(Thread.java:595)
Caused by: javax.transaction.RollbackException
     at com.evermind.server.ApplicationServerTransaction.checkForRollbackOnlyWhileInCommit(ApplicationServerTransaction.java:582)
     at com.evermind.server.ApplicationServerTransaction.doCommit(ApplicationServerTransaction.java:244)
     at com.evermind.server.ApplicationServerTransaction.commit(ApplicationServerTransaction.java:130)
     at com.evermind.server.ApplicationServerTransactionManager.commit(ApplicationServerTransactionManager.java:433)
     at com.evermind.server.ejb.EJBTransactionManager.end(EJBTransactionManager.java:132)
     ... 29 more
<2007-03-21 12:38:26,458> <ERROR> <default.collaxa.cube.engine.dispatch> <BaseScheduledWorker::process> Fallo al manejar el mensaje de distribución ... excepción ORABPEL-05002
Error del manejador de mensajes.
Se ha producido una excepción al intentar procesar el mensaje "com.collaxa.cube.engine.dispatch.message.invoke.InvokeInstanceMessage"; la excepción es: An exception occurred during transaction completion: ; nested exception is: javax.transaction.RollbackException
ORABPEL-05002
Error del manejador de mensajes.
Se ha producido una excepción al intentar procesar el mensaje "com.collaxa.cube.engine.dispatch.message.invoke.InvokeInstanceMessage"; la excepción es: An exception occurred during transaction completion: ; nested exception is: javax.transaction.RollbackException
     at com.collaxa.cube.engine.dispatch.DispatchHelper.handleMessage(DispatchHelper.java:171)
     at com.collaxa.cube.engine.dispatch.BaseScheduledWorker.process(BaseScheduledWorker.java:70)
     at com.collaxa.cube.engine.ejb.impl.WorkerBean.onMessage(WorkerBean.java:86)
     at sun.reflect.GeneratedMethodAccessor66.invoke(Unknown Source)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:585)
     at com.evermind.server.ejb.interceptor.joinpoint.EJBJoinPointImpl.invoke(EJBJoinPointImpl.java:35)
     at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
     at com.evermind.server.ejb.interceptor.system.DMSInterceptor.invoke(DMSInterceptor.java:52)
     at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
     at com.evermind.server.ejb.interceptor.system.SetContextActionInterceptor.invoke(SetContextActionInterceptor.java:44)
     at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
     at com.evermind.server.ejb.InvocationContextPool.invoke(InvocationContextPool.java:55)
     at oracle.j2ee.connector.messageinflow.MessageEndpointImpl.OC4J_invokeMethod(MessageEndpointImpl.java:297)
     at WorkerBean_EndPointProxy_4bin6i8.onMessage(Unknown Source)
     at oracle.j2ee.ra.jms.generic.WorkConsumer.run(WorkConsumer.java:266)
     at oracle.j2ee.connector.work.WorkWrapper.runTargetWork(WorkWrapper.java:242)
     at oracle.j2ee.connector.work.WorkWrapper.doWork(WorkWrapper.java:215)
     at oracle.j2ee.connector.work.WorkWrapper.run(WorkWrapper.java:190)
     at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:814)
     at java.lang.Thread.run(Thread.java:595)
I've been looking through the Internet but i haven't found anything. this same process has been working, so I don't understand anything. Please, can anyone help me? thank you very much.

It sounds like the BPEL process is failing. Is there an error instance n the BPEL console? Can you test the BPEL process standalone from the BPEL console?

Error when calling BPEL from ESB in clustered environment

Hi
We have recently installed SOA Suite in a clustered environment and have a serious issue.
I am not able to call BPEL processes from my ESB services via WSIF (by using the 'browse target operation' in JDeveloper). The exception i get at runtime is this.
"javax.naming.NameNotFoundException: ejb/collaxa/system/DeliveryBean not found"
When I instead call the BPEL process via SOAP (by using a SOAP invocation service i JDeveloper) it works fine.
Everything works fine in development environment which not are clustered.
Has anyone any excperience from using ESB in a clustered environment?
Regards
Kalle Viklund

Hi
ESB and BPEL resides in the same oc4j-instance. Though, esb-rt and orabpel are different applications in that oc4j-instance. And the lookup 'ejb/collaxa/system/DeliveryBean' only exists in the orabpel application.
In the ESB Console I already have the same setting for the 'BPELSystem' as for the 'Defaultsystem'.
Cluster name: esb_prod
Virtual host: prod1.sth.nu
Port: 80
Topic location: ESBTopics/Topics/ESB_JAVA_DEFERRED
Connection factory location: OracleOJMS/XATCF
regards
Kalle

Error Calling BPEL from ESB

I am using the SOA Suite and have a very simple ESB project which picks up files from a directory and calls a BPEL process following a simple XSL translation. I am getting the following error:
An unhandled exception has been thrown in the ESB system. The exception reported is: "java.lang.Exception: Failed to create "ejb/collaxa/system/DeliveryBean" bean; exception reported is: "javax.naming.NamingException: Lookup error: javax.naming.AuthenticationException: Not authorized; nested exception is: javax.naming.AuthenticationException: Not authorized [Root exception is javax.naming.AuthenticationException: Not authorized] at com.evermind.server.rmi.RMIClientContext.lookup(RMIClientContext.java:64) at javax.naming.InitialContext.lookup(InitialContext.java:351) at com.oracle.bpel.client.util.BeanRegistry.lookupDeliveryBean(BeanRegistry.java:279) at com.oracle.bpel.client.delivery.DeliveryService.getDeliveryBean(DeliveryService.java:250) at com.oracle.bpel.client.delivery.DeliveryService.post(DeliveryService.java:174) at com.oracle.bpel.client.delivery.DeliveryService.post(DeliveryService.java:158) at oracle.tip.esb.server.service.impl.bpel.BPELService.processBusinessEvent(Unknown Source) at oracle.tip.esb.server.dispatch.InitialEventDispatcher.dispatchNonRoutingService(Unknown Source) at oracle.tip.esb.server.dispatch.InitialEventDispatcher.dispatch(Unknown Source) at oracle.tip.esb.server.dispatch.BusinessEvent.raise(Unknown Source) at oracle.tip.esb.utils.EventUtils.raiseBusinessEvent(Unknown Source) at oracle.tip.esb.server.service.EsbRouterSubscription.onBusinessEvent(Unknown Source) at oracle.tip.esb.server.dispatch.EventDispatcher.executeSubscription(Unknown Source) at oracle.tip.esb.server.dispatch.InitialEventDispatcher.processSubscription(Unknown Source) at oracle.tip.esb.server.dispatch.InitialEventDispatcher.processSubscriptions(Unknown Source) at oracle.tip.esb.server.dispatch.EventDispatcher.dispatchRoutingService(Unknown Source) at oracle.tip.esb.server.dispatch.InitialEventDispatcher.dispatch(Unknown Source) at oracle.tip.esb.server.dispatch.BusinessEvent.raise(Unknown Source) at oracle.tip.esb.utils.EventUtils.raiseBusiness
The esb has been deployed to our server (OAS 10.1.3) using jdeveloper. Please can anybody point me in the right direction.

Not really. There are 2 ways to invoke BPEL.
1) Over SOAP using an ESB SOAP service that parses a BPLE WSDL. This works like any standard HTTP/SOAP invocation and would be used when BPEL and ESB are not in the same container.
2) Over Java by add a routing rule to an ESB Routing Servie and select a BPEL process in the BPELSystem as the target. This is the preferred binding when ESB and BPEL are colocate din the same container. This takes advantage of the fact that ESB kistens on the BPEL internal Control jms queue when a BPEL process is deployed into the container. That is how the BPEL processes show up in the BPELSystem ESB service tree.

Response not coming back to ESB when calling BPEL process

Hi,
I am doing some demo,
the actual process is, in ESB, I am reading a file and passing thsoe fiel contents to BPEL as SOAP service. In BPEL proecess, I processed the message and sending the response back to the ESB. When I deployed and check the process flow in the BPEL console, everything looks fine, I mena, it sending the response back to the ESB, where as in ESB process, I am not able to see the response.
Is there any thing that I am missing?
Thanks.

Is the BPEL process a synchronous process?
Also for performance reasons it it best to call BPEL process via the direct jca connector not SOAP.
You do this by just selecting the BPEL process in the routing service going through the wizard. There is no need to creat a SOAP service. The good this about this is that in the ESB process it provides a link to the BPEL process.
cheers
James

Calling BPEL WSDL form ESB(Urgent)

Hi,
Firstly I am new to BPEL. This question might be very simple. I need the solution ASAP.
Coming to the usecase.
I have one service "A" in ESB and other service "B" in BPEL. To make it simple I need to listen a file using a file adapter in service "A"(ESB) and route the values to other service "B" (BPEL) and insert in to database using a database adapter.
Can this be possible. If so can any one please provide me pointers to create the services in ESB and BPEL to execute the above usecase.
Thanks
Rao.

Hi,
Thats not that difficult.
The steps to undertake are :
1.create a bpel proces which accepts your format as input. and write it to your database either calling a stored procedure or insert the data right into a table.
2. deploy this project to your app server and test it using the BPELConsole. This way you can make sure your BPEL project works.
3. create an ESB process which reads a file ( the file adapter ). You'll get a Routing Service for free.
4. Double click on the routing service, press the green + sign to add a routing rule. Select the service browser. browse your BPEL system and select the BPEL process you deployed in step 2.
5. Create the mapper file to map the input of your file adapter to the input of your BPEL process
6. Deploy your ESB process.
And you should be ready to go.
HTH
Edit :
You can also use a SOAP Service as the previous poster mentioned. There are a few ways to tie ESB and BPEL together. One is by using SOAP the other is by calling the BPEL process directly ( internally the data then flows over a RMI connection ).
Message was edited by:
Martin.Kleinman

Calling BPEL WSDL in ESB

Hi,
Firstly I am new to BPEL. This question might be very simple. I need the solution ASAP.
Coming to the usecase.
I have one service "A" in ESB and other service "B" in BPEL. To make it simple I need to listen a file using a file adapter in service "A"(ESB) and route the values to other service "B" (BPEL) and insert in to database using a database adapter.
Can this be possible. If so can any one please provide me pointers to create the services in ESB and BPEL to execute the above usecase.
Thanks
Rao.

Hi,
Thats not that difficult.
The steps to undertake are :
1.create a bpel proces which accepts your format as input. and write it to your database either calling a stored procedure or insert the data right into a table.
2. deploy this project to your app server and test it using the BPELConsole. This way you can make sure your BPEL project works.
3. create an ESB process which reads a file ( the file adapter ). You'll get a Routing Service for free.
4. Double click on the routing service, press the green + sign to add a routing rule. Select the service browser. browse your BPEL system and select the BPEL process you deployed in step 2.
5. Create the mapper file to map the input of your file adapter to the input of your BPEL process
6. Deploy your ESB process.
And you should be ready to go.
HTH
Edit :
You can also use a SOAP Service as the previous poster mentioned. There are a few ways to tie ESB and BPEL together. One is by using SOAP the other is by calling the BPEL process directly ( internally the data then flows over a RMI connection ).
Message was edited by:
Martin.Kleinman

Calling BPEL Process From ESB

Hi Gurus,
I'm experiencing an issue calling a BPEL process using the ESB SOAP Service. Basically, the ESB calls the BPEL process and manages to pass the message to the asychronous BPEL process however the first step in the BPEL process after the Recieve, an Assign, always fails with an Xpath error saying that the attribute being mapped is blank. However, when I look at the Recieve step I can see the value for this attribute. I can Initiate the BPEL process manually and enter the same values and these process successfully.
Has anyone encountered this issue previously or know what I'm doing wrong?
Any assistance appreciated.
Pete

Hi there,
I am getting the same issue. I have two bpel processes, the first processplaces data into a common .xsd format and then sends it over to another process with is expeting the same .xsd format.
I'm pretty sure i know what the issue is, but i'm not sure what the philosophy behind the whole thing is and how it is solved.
When i transfrom the data over to the common .xsd is allocated a namespace ns0 which is then prepended to each element. When this is sent to the other process this stays prepended. The data is then allocated to the common .xsd in the second process with is allocated another namespace ns3.
So when you try an assign is searching for ns3:rootElemnt....... which doesn't exist as it as the ns0 carried over from the first process.
Is this correct? What do we do to get round it?
Thanks,

ESB Polling: bpel calling order and limitations

We work with a SOA 10.1.3.3 application:
Problems:
1) one ESB polling service calls different BPEL services.
Is it possible to force the order of the BPEL CALLS (and execution) following the order of the records in the polling table ?
(The BPEL instance doesn't follow the polling order).
The "ORDER BY " property of esb service is correctly set.
2) Is it possible to limit the number of BPEL CALLS for each polling step ?
In order to test the polling parameter we set the polling parameter as follow:
- Polling frequency = 10 sec
- Database Rows per XML Document = 1
- Database Rows per Transaction = 1
If the number of polling records is 40 (for example) ESB call up to 40 BPEL in one polling step.
Thanks in advance
Umberto

Can anyone help me for this problem ?

Error while calling a bpel service from OSB

Hi
I try to call a BPEL service from OSB 10.3 and use these bpel url's
ormi://<hostname>:<rmi port>/<domain name>/<process name>
opmn://<hostname>:<opmn port>/<oc4j instance name>/<domain name>/<process name>
and I create a static service account with ocj4admin
when I try to run the BusinessService then I got this error
WARNING: Exception returned by remote server: {0}
com.evermind.server.rmi.RMIConnectionException: Disconnected: javax.xml.namespace.QName; local class incompatible: stream classdesc serialVersionUID = -91204487
54896609940, local class serialVersionUID = -916876369326528164
at com.evermind.server.rmi.RmiCallQueue.notifyQueuedThreads(RmiCallQueue.java:70)
at com.evermind.server.rmi.RMIClientConnection.notifyQueuedThreads(RMIClientConnection.java:208)
at com.evermind.server.rmi.RMIClientConnection.resetState(RMIClientConnection.java:147)
at com.evermind.server.rmi.RMIConnection.receiveDisconnect(RMIConnection.java:236)
at com.evermind.server.rmi.RMIClientConnection.receiveDisconnect(RMIClientConnection.java:176)
at com.evermind.server.rmi.RMIConnection.handleOrmiCommand(RMIConnection.java:208)
Please help me out.I am using SOA Server 10.1.3.4 with jdk 1.4.
Regards
Ayush
Edited by: Ayush fujitsu on Apr 6, 2010 3:36 AM

Hi i have followed the following steps which is specified in this thread
You need to follow below steps...
add a java parameter to the OSB server. Go to domains\osb_domain\bin folder and edit the setDomainEnv file and add this line to this file. set JAVA_PROPERTIES=-Dplatform.home=%WL_HOME% -Dwls.home=%WLS_HOME% -Dweblogic.home=%WLS_HOME% -Dcom.sun.xml.namespace.QName.useCompatibleSerialVersionUID=1.0
Step 2 is to replace the bpel jars in the bpel transport ear. Go folder osb_10.3\lib\transports and open bpel10gtransport.ear and replace the following jar files orabpel.jar, orabpel-common.jar , xmlparserv2.jar and oc4jclient.jar with the ones you can find in the soa suite 10.1.3 home.
But still i am getting the error.
I am using WLS (10.0).Is it compatible with bpel-10g protocol, because i have already called a sync BPEL process with http protocol and it worked?This thread talks about WLS(9.2)
Regards
Ayush

Calling Web Service with SOAP header from BPEL

Hi,
I am calling a web service (with header information) from BPEL. In the Invoke activity, i created a header variable to pass the header information.
But, when i test the BPEL service, invoke activity fails because the header information is not being passed.
Below is the error message (copied from clipboard).
+<messages><input><Invoke_1_getsubinfo_InputVariable><part xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" name="parameters"><getsubinfoElement xmlns="http://ws/its/tabs/webservices/SingleRowWS/SingleRowWS.wsdl">+
+<pSubnoin>+
+<insubno>12345678</insubno>+
+</pSubnoin>+
+</getsubinfoElement>+
+</part></Invoke_1_getsubinfo_InputVariable></input><fault><bindingFault xmlns="http://schemas.oracle.com/bpel/extension"><part name="summary"><summary>exception on JaxRpc invoke:+
start fault message:+
Internal Server Error (Caught exception while handling request: javax.xml.rpc.JAXRPCException: Not authenticated user)+
*:end fault message*</summary>
+</part></bindingFault></fault></messages>+
As said, no header information is visible in the Invoke activity.
Please provide help for the above issue.
-MJ

Hello Patrick,
Thanks for the response. I am using normal assign activity to assign values to the header variable as shown below. HeadMT is the header variable which is passed in the invoke activity.
+<assign name="Assign_Header">+
+<copy>+
+<from expression="'tkl12'"/>+
+<to query="/ns1:LOGIN_INFO/ns1:USER_NAME" variable="*HeadMT*"+
part="payload"/>
+</copy>+
+<copy>+
+<from expression="'tkl123'"/>+
+<to query="/ns1:LOGIN_INFO/ns1:PASSWORD" variable="*HeadMT*"+
part="payload"/>
+</copy>+
+<copy>+
+<from expression="'TKL'"/>+
+<to query="/ns1:LOGIN_INFO/ns1:CHANNEL_ID" variable="*HeadMT*"+
part="payload"/>
+</copy>+
+</assign>+
The expected input by the web service is as below with the header information highlighted.
+<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ns1="http://ws/webservices/RowWS/RowWS.wsdl">+
+*<soap:Header>*+
+*<ns1:LOGIN_INFO>*+
+*<ns1:USERNAME>tkl12</ns1:USERNAME>*+
+*<ns1:PASSWORD>tkl123</ns1:PASSWORD>*+
+*<ns1:CHANNEL_ID>TKL</ns1:CHANNEL_ID>*+
+*</ns1:LOGIN_INFO>*+
+*</soap:Header>*+
+<soap:Body>+
+<ns1:substatusElement>+
+<ns1:pInparam>+
+<ns1:insubno>7674988</ns1:insubno>+
+</ns1:pInparam>+
+</ns1:substatusElement>+
+</soap:Body>+
+</soap:Envelope>+

Error calling BPEL from ESB Multi-part simple type

I am trying to define a soap service in ESB which is refering a BPEL service. I get the error
The selected porttype is using a message that is invalid for ESB because it is multi-part or has a simple type.The message RuntimeFaultMessage in operation process of port type exportCaCustomers is invalid. Please select another portype.
Here is the wsdl for the BPEL service. exportCaCustomers.wsdl
<definitions
name="exportCaCustomers"
targetNamespace="http://xmlns.oracle.com/exportCaCustomers"
xmlns="http://schemas.xmlsoap.org/wsdl/"
xmlns:ns1="http://www.globalcompany.com/ns/order"
xmlns:plnk="http://schemas.xmlsoap.org/ws/2003/05/partner-link/"
xmlns:ns3="http://usconcrete.com/v1/interfaces/common/InputMessage.xsd"
xmlns:ns2="http://schemas.oracle.com/bpel/extension"
xmlns:bpelx="http://schemas.oracle.com/bpel/extension"
xmlns:client="http://xmlns.oracle.com/exportCaCustomers"
xmlns:ns10="http://usconcrete.com/v1/interfaces/common/InputMessage.xsd"
>
<import namespace="http://schemas.oracle.com/bpel/extension" location="RuntimeFault.wsdl"/>
<types>
<schema xmlns="http://www.w3.org/2001/XMLSchema" xmlns:ns1="http://www.globalcompany.com/ns/order"
xmlns:plnk="http://schemas.xmlsoap.org/ws/2003/05/partner-link/" xmlns:client="http://xmlns.oracle.com/exportCaCustomers">
<import namespace="http://xmlns.oracle.com/exportCaCustomers" schemaLocation="exportCaCustomers.xsd"/>
</schema>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:ns1="http://www.globalcompany.com/ns/order"
xmlns:plnk="http://schemas.xmlsoap.org/ws/2003/05/partner-link/" xmlns:client="http://xmlns.oracle.com/exportCaCustomers">
<xsd:import namespace="http://www.globalcompany.com/ns/order" schemaLocation="sampleTax.xsd"/>
</xsd:schema>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<xsd:import namespace="http://usconcrete.com/v1/interfaces/common/InputMessage.xsd" schemaLocation="InputMessage.xsd"/>
</xsd:schema>
</types>
<message name="exportCaCustomersRequestMessage">
<part name="payload" element="ns10:CVInputMessage"/>
</message>
<message name="exportCaCustomersResponseMessage">
<part name="payload" element="client:exportCaCustomersProcessResponse"/>
</message>
<portType name="exportCaCustomers">
<operation name="process">
<input message="client:exportCaCustomersRequestMessage"/>
<output message="client:exportCaCustomersResponseMessage"/>
<fault name="bindingFault" message="ns2:RuntimeFaultMessage"/>
</operation>
</portType>
<plnk:partnerLinkType name="exportCaCustomers">
<plnk:role name="exportCaCustomersProvider">
<plnk:portType name="client:exportCaCustomers"/>
</plnk:role>
</plnk:partnerLinkType>
</definitions>
These are the contents of RuntimeFault.wsdl
<?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>
This looks like a very basic thing to do. My BPEL process is working fine. I just want to access it from ESB. Any ESB gurus there. Please respond.

<fault name="bindingFault" message="ns2:RuntimeFaultMessage"/>Don't think this is the way to define the RuntimeFaults.
the fault-element you use to 'throw' you own business faults.
RunTimeFaults are handled by the bpel framework itself and aren't throwable like this.
See :
http://www.oracle.com/technology/products/ias/bpel/htdocs/orabpel_technotes.tn007.html
""Business faults are application specific faults and occur when an explicit <throw> activity is executed or an <invoke> activity gets a fault as response. The fault name of a business fault is specified by the BPEL process and the messageType, if one exists, is defined in the WSDL.
Runtime faults are not user defined and will not appear in the WSDL for a process or service.""

ESB calling BPEL service

Similar Messages

Maybe you are looking for