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

Similar Messages

  • 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 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,

  • 401 Unauthorized:HTTP transport error while calling external WSDL from BPEL

    Hi,
    I have simple BPEL process whic calls siebel WSDL file through partner link.
    I have successfully compiled and deployed BPEL process, when i initiate the Process, instace got errored out at invoke activity.
    Error Goes like this
    "<remoteFault xmlns="http://schemas.oracle.com/bpel/extension"><part name="summary"><summary>
    exception on JaxRpc invoke: HTTP transport error: javax.xml.soap.SOAPException:
    java.security.PrivilegedActionException: javax.xml.soap.SOAPException: Bad response: 401 Unauthorized</summary>
    </part></remoteFault>"
    Can anybody help on this issue, Could you please give me possible solution.
    Thank youl.

    we have not provided any authentication credentials to XMLSpy, we have just uploaded siebel WSDL file then sent the SOAP request with some customer Id then we have received proper response with all desired customer data.
    In the same way we tried to call same siebel WSDL file from BPEL process throgh partner link. errored instance has created with 401 unauthorised HTTP transport error..
    Do you think is this probem at siebel application side?
    We have deployed our BPEL process to SOA server which is having HTTP port 7777.
    as per my investigation,i found that we have to open port from siebel side (which WSDL file we are calling) which matches with above HTTP port number.
    Do you have any idea on this above clue? Please let us know more details on this.

  • 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

  • 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

  • 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.

  • Error while calling a procedure from ESB

    Hi,
    I am calling a procedure from ESB using DB adapter. and in the routing rules i am mapping the i/p values for schema to procedure input variables using mappings(transformation) but the values are going as null to the procedure call.
    Please help me out.
    The exception follows...
    An unhandled exception has been thrown in the ESB system. The exception reported is: "org.collaxa.thirdparty.apache.wsif.WSIFException: esb:///ESB_Projects/ESB-Issues_issue3/db3.wsdl [ db3_ptt::db3(InputParameters,OutputParameters) ] - WSIF JCA Execute of operation 'db3' failed due to: Error while trying to prepare and execute an API.
    An error occurred while preparing and executing the SYSTEM.INSERT_ISSUE_PROC API. Cause: java.sql.SQLException: ORA-01400: cannot insert NULL into ("SYSTEM"."ISSUES"."ISSUE_NAME")
    ORA-06512: at "SYSTEM.INSERT_ISSUE_PROC", line 16
    ORA-06512: at line 1
    [Caused by: ORA-01400: cannot insert NULL into ("SYSTEM"."ISSUES"."ISSUE_NAME")
    ORA-06512: at "SYSTEM.INSERT_ISSUE_PROC", line 16                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           

    This is likely being caused by a problem that we've seen a number of times. You'll have namespace issues and problems with NULLs if your JDev is 10.1.3.1 and SOA is 10.1.3.3 (or vice-versa). You MUST synchronize JDev 10.1.3.3 (or higher) with SOA 10.1.3.3 (or higher). It doesn't matter if you mix 10.1.3.3 and 10.1.3.4. You just need to get away from 10.1.3.1.

  • Error while initiating a bpel process through ESB....

    Hi,
    I initiated a BPEL process from ESB(which is a sync process)...which in turn calls a async process which contains the JMS queues....While running the process...i am getting the below mentioned error.....
    <env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"><env:Header/><env:Body><env:Fault xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"><faultcode>env:ESBMessageProcessingFailed</faultcode><detail><EventName>DefaultSystem.RoutingService.outOfService</EventName><Cause>An unhandled exception has been thrown in the ESB system. The exception reported is: "oracle.tip.esb.server.common.exceptions.BusinessEventFatalException: An unhandled exception has been thrown in the ESB system. The exception reported is: "com.oracle.bpel.client.delivery.ReceiveTimeOutException: Waiting for response has timed out. The conversation id is 83076650D00F11DDBFFD0151085C6DFB. Please check the process instance for detail.
         at com.evermind.server.rmi.RMICall.EXCEPTION_ORIGINATES_FROM_THE_REMOTE_SERVER(RMICall.java:109)
         at com.evermind.server.rmi.RMICall.throwRecordedException(RMICall.java:125)
         at com.evermind.server.rmi.RMIClientConnection.obtainRemoteMethodResponse(RMIClientConnection.java:517)
         at com.evermind.server.rmi.RMIClientConnection.invokeMethod(RMIClientConnection.java:461)
         at com.evermind.server.rmi.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:63)
         at com.evermind.server.rmi.RecoverableRemoteInvocationHandler.invoke(RecoverableRemoteInvocationHandler.java:28)
         at com.evermind.server.ejb.StatelessSessionRemoteInvocationHandler.invoke(StatelessSessionRemoteInvocationHandler.java:43)
         at __Proxy7.request(Unknown Source)
         at com.oracle.bpel.client.delivery.DeliveryService.request(DeliveryService.java:104)
         at com.oracle.bpel.client.delivery.DeliveryService.request(DeliveryService.java:67)
         at oracle.tip.esb.server.service.impl.bpel.BPELService.processBusinessEvent(BPELService.java:380)
         at oracle.tip.esb.server.dispatch.InitialEventDispatcher.dispatchNonRoutingService(InitialEventDispatcher.java:106)
         at oracle.tip.esb.server.dispatch.InitialEventDispatcher.dispatch(InitialEventDispatcher.java:85)
         at oracle.tip.esb.server.dispatch.BusinessEvent.raise(BusinessEvent.java:1416)
         at oracle.tip.esb.utils.EventUtils.raiseBusinessEvent(EventUtils.java:105)
         at oracle.tip.esb.server.service.EsbRouterSubscription.onBusinessEvent(EsbRouterSubscription.java:273)
         at oracle.tip.esb.server.dispatch.EventDispatcher.executeSubscription(EventDispatcher.java:138)
         at oracle.tip.esb.server.dispatch.InitialEventDispatcher.processSubscription(InitialEventDispatcher.java:212)
         at oracle.tip.esb.server.dispatch.InitialEventDispatcher.processSubscriptions(InitialEventDispatcher.java:197)
         at oracle.tip.esb.server.dispatch.EventDispatcher.dispatchRoutingService(EventDispatcher.java:94)
         at oracle.tip.esb.server.dispatch.InitialEventDispatcher.dispatch(InitialEventDispatcher.java:82)
         at oracle.tip.esb.server.dispatch.BusinessEvent.raise(BusinessEvent.java:1416)
         at oracle.tip.esb.server.service.impl.soap.EventOracleSoapProvider.raiseEvent(EventOracleSoapProvider.java:314)
         at oracle.tip.esb.server.service.impl.soap.EventOracleSoapProvider.processMessage(EventOracleSoapProvider.java:187)
         at oracle.j2ee.ws.server.provider.ProviderProcessor.doEndpointProcessing(ProviderProcessor.java:956)
         at oracle.j2ee.ws.server.WebServiceProcessor.invokeEndpointImplementation(WebServiceProcessor.java:349)
         at oracle.j2ee.ws.server.provider.ProviderProcessor.doRequestProcessing(ProviderProcessor.java:466)
         at oracle.j2ee.ws.server.WebServiceProcessor.processRequest(WebServiceProcessor.java:114)
         at oracle.j2ee.ws.server.WebServiceProcessor.doService(WebServiceProcessor.java:96)
         at oracle.j2ee.ws.server.WebServiceServlet.doPost(WebServiceServlet.java:177)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:763)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
         at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:713)
         at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:370)
         at com.evermind.server.http.HttpRequestHandler.doProcessRequest(HttpRequestHandler.java:871)
         at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:453)
         at com.evermind.server.http.HttpRequestHandler.serveOneRequest(HttpRequestHandler.java:221)
         at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:122)
         at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:111)
         at oracle.oc4j.network.ServerSocketReadHandler$SafeRunnable.run(ServerSocketReadHandler.java:260)
         at oracle.oc4j.network.ServerSocketAcceptHandler.procClientSocket(ServerSocketAcceptHandler.java:239)
         at oracle.oc4j.network.ServerSocketAcceptHandler.access$700(ServerSocketAcceptHandler.java:34)
         at oracle.oc4j.network.ServerSocketAcceptHandler$AcceptHandlerHorse.run(ServerSocketAcceptHandler.java:880)
         at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:303)
         at java.lang.Thread.run(Thread.java:595)
    Caused by: com.oracle.bpel.client.delivery.ReceiveTimeOutException: Waiting for response has timed out. The conversation id is 83076650D00F11DDBFFD0151085C6DFB. Please check the process instance for detail.
         at com.collaxa.cube.engine.delivery.DeliveryHandler.initialRequestAnyType(DeliveryHandler.java:534)
         at com.collaxa.cube.engine.delivery.DeliveryHandler.initialRequest(DeliveryHandler.java:457)
         at com.collaxa.cube.engine.delivery.DeliveryHandler.request(DeliveryHandler.java:131)
         at com.collaxa.cube.ejb.impl.DeliveryBean.request(DeliveryBean.java:95)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         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.JAASInterceptor$1.run(JAASInterceptor.java:31)
         at java.security.AccessController.doPrivileged(Native Method)
         at javax.security.auth.Subject.doAs(Subject.java:396)
         at com.evermind.server.ThreadState.runAs(ThreadState.java:648)
         at com.evermind.server.ejb.interceptor.system.JAASInterceptor.invoke(JAASInterceptor.java:34)
         at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
         at com.evermind.server.ejb.interceptor.system.TxRequiredInterceptor.invoke(TxRequiredInterceptor.java:50)
         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 DeliveryBean_RemoteProxy_4bin6i8.request(Unknown Source)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:585)
         at com.evermind.server.rmi.RmiMethodCall.run(RmiMethodCall.java:53)
         ... 2 more
         at oracle.tip.esb.server.service.impl.bpel.BPELService.processBusinessEvent(BPELService.java:473)
         at oracle.tip.esb.server.dispatch.InitialEventDispatcher.dispatchNonRoutingService(InitialEventDispatcher.java:106)
         at oracle.tip.esb.server.dispatch.InitialEventDispatcher.dispatch(InitialEventDispatcher.java:85)
         at oracle.tip.esb.server.dispatch.BusinessEvent.raise(BusinessEvent.java:1416)
         at oracle.tip.esb.utils.EventUtils.raiseBusinessEvent(EventUtils.java:105)
         at oracle.tip.esb.server.service.EsbRouterSubscription.onBusinessEvent(EsbRouterSubscription.java:273)
         at oracle.tip.esb.server.dispatch.EventDispatcher.executeSubscription(EventDispatcher.java:138)
         at oracle.tip.esb.server.dispatch.InitialEventDispatcher.processSubscription(InitialEventDispatcher.java:212)
         at oracle.tip.esb.server.dispatch.InitialEventDispatcher.processSubscriptions(InitialEventDispatcher.java:197)
         at oracle.tip.esb.server.dispatch.EventDispatcher.dispatchRoutingService(EventDispatcher.java:94)
         at oracle.tip.esb.server.dispatch.InitialEventDispatcher.dispatch(InitialEventDispatcher.java:82)
         at oracle.tip.esb.server.dispatch.BusinessEvent.raise(BusinessEvent.java:1416)
         at oracle.tip.esb.server.service.impl.soap.EventOracleSoapProvider.raiseEvent(EventOracleSoapProvider.java:314)
         at oracle.tip.esb.server.service.impl.soap.EventOracleSoapProvider.processMessage(EventOracleSoapProvider.java:187)
         at oracle.j2ee.ws.server.provider.ProviderProcessor.doEndpointProcessing(ProviderProcessor.java:956)
         at oracle.j2ee.ws.server.WebServiceProcessor.invokeEndpointImplementation(WebServiceProcessor.java:349)
         at oracle.j2ee.ws.server.provider.ProviderProcessor.doRequestProcessing(ProviderProcessor.java:466)
         at oracle.j2ee.ws.server.WebServiceProcessor.processRequest(WebServiceProcessor.java:114)
         at oracle.j2ee.ws.server.WebServiceProcessor.doService(WebServiceProcessor.java:96)
         at oracle.j2ee.ws.server.WebServiceServlet.doPost(WebServiceServlet.java:177)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:763)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
         at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:713)
         at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:370)
         at com.evermind.server.http.HttpRequestHandler.doProcessRequest(HttpRequestHandler.java:871)
         at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:453)
         at com.evermind.server.http.HttpRequestHandler.serveOneRequest(HttpRequestHandler.java:221)
         at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:122)
         at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:111)
         at oracle.oc4j.network.ServerSocketReadHandler$SafeRunnable.run(ServerSocketReadHandler.java:260)
         at oracle.oc4j.network.ServerSocketAcceptHandler.procClientSocket(ServerSocketAcceptHandler.java:239)
         at oracle.oc4j.network.ServerSocketAcceptHandler.access$700(ServerSocketAcceptHandler.java:34)
         at oracle.oc4j.network.ServerSocketAcceptHandler$AcceptHandlerHorse.run(ServerSocketAcceptHandler.java:880)
         at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:303)
         at java.lang.Thread.run(Thread.java:595)
    Caused by: com.oracle.bpel.client.delivery.ReceiveTimeOutException: Waiting for response has timed out. The conversation id is 83076650D00F11DDBFFD0151085C6DFB. Please check the process instance for detail.
         at com.evermind.server.rmi.RMICall.EXCEPTION_ORIGINATES_FROM_THE_REMOTE_SERVER(RMICall.java:109)
         at com.evermind.server.rmi.RMICall.throwRecordedException(RMICall.java:125)
         at com.evermind.server.rmi.RMIClientConnection.obtainRemoteMethodResponse(RMIClientConnection.java:517)
         at com.evermind.server.rmi.RMIClientConnection.invokeMethod(RMIClientConnection.java:461)
         at com.evermind.server.rmi.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:63)
         at com.evermind.server.rmi.RecoverableRemoteInvocationHandler.invoke(RecoverableRemoteInvocationHandler.java:28)
         at com.evermind.server.ejb.StatelessSessionRemoteInvocationHandler.invoke(StatelessSessionRemoteInvocationHandler.java:43)
         at __Proxy7.request(Unknown Source)
         at com.oracle.bpel.client.delivery.DeliveryService.request(DeliveryService.java:104)
         at com.oracle.bpel.client.delivery.DeliveryService.request(DeliveryService.java:67)
         at oracle.tip.esb.server.service.impl.bpel.BPELService.processBusinessEvent(BPELService.java:380)
         ... 34 more
    Caused by: com.oracle.bpel.client.delivery.ReceiveTimeOutException: Waiting for response has timed out. The conversation id is 83076650D00F11DDBFFD0151085C6DFB. Please check the process instance for detail.
         at com.collaxa.cube.engine.delivery.DeliveryHandler.initialRequestAnyType(DeliveryHandler.java:534)
         at com.collaxa.cube.engine.delivery.DeliveryHandler.initialRequest(DeliveryHandler.java:457)
         at com.collaxa.cube.engine.delivery.DeliveryHandler.request(DeliveryHandler.java:131)
         at com.collaxa.cube.ejb.impl.DeliveryBean.request(DeliveryBean.java:95)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         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.JAASInterceptor$1.run(JAASInterceptor.java:31)
         at java.security.AccessController.doPrivileged(Native Method)
         at javax.security.auth.Subject.doAs(Subject.java:396)
         at com.evermind.server.ThreadState.runAs(ThreadState.java:648)
         at com.evermind.server.ejb.interceptor.system.JAASInterceptor.invoke(JAASInterceptor.java:34)
         at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
         at com.evermind.server.ejb.interceptor.system.TxRequiredInterceptor.invoke(TxRequiredInterceptor.java:50)
         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 DeliveryBean_RemoteProxy_4bin6i8.request(Unknown Source)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:585)
         at com.evermind.server.rmi.RmiMethodCall.run(RmiMethodCall.java:53)
         ... 2 more
    </Cause></detail></env:Fault></env:Body></env:Envelope>
    kindly provide me the solution....
    Regards,
    Suresh K

    As I stated in my previous post, there is an issue with the BPEL process not responding back to ESB in a timely manner.
    Unfortunately I don't have your process infront of me so it will require some thinking on your behalf to undersatnd how and why this may be happening.
    Things to ask yourself.
    - Is the data getting past correctly from the ESB to BPEL
    - What happend to the BPEL process that the ESB called
    - Is the ESB calling the BPEL process you are expecting, check server, and bpel versions
    - What does the opmn or domain logs say
    cheers
    James

  • How to propagate a BPEL fault into ESB

    Hi
    I have a problem with getting errors that occur in my BPEL process propagate up to the calling ESB service.
    I have an ESB service that via a routing rule invokes a BPEL process.
    I'm using direct Java-call (i think) between ESB and BPEL by simply choosing the BPEL process via the browser in the Routing Rule (BPELSystem/default/myBPELProcess/etc...). BPEL and ESB resides in the same container.
    The BPEL process basically just inserts some data in the database using the DB adapter. If something goes wrong this this insert (unique key violation, etc) I would like the error to be propagated up to the ESB.
    I have tried using both synchronous and asynchronous execution in my Routing Rule, and I have tried setting the Endpoint Property 'InvocationMode' to 'local'. I have also tried to set the property 'transaction' to 'participate' in the bpel.xml of my BPEL process. Nothing makes the fault in the BPEL process propagate up to my ESB service.
    What do I have to do in order to achieve this? I would like this error to propagate up the the ESB so that I can retry BPEL process when the error is fixed.
    Any ideas?
    Regards
    Kalle

    Hi Kalle,
    which version of SOA Suite are you using?
    Have a look to latest patchset (10.1.3.3 and patch 6723162 on metalink) - I guess there were some fixes for fault propragation.
    Hope this helps,
    Ivan

  • Call Bpel process through HTTP get or post method

    I need to call BPEL process from Mobile.
    In mobile we are using HTTP get or post methods. so can anybody tell me how to invoke BPEL(how to pass input to BPEL) by using HTTP get or post method.
    Vivek garg
    Edited by: 809104 on Dec 24, 2010 2:36 AM

    I got the soluntion
    we just need to change the binding in WSDL file from Soap to HTTP.
    First of all add three namespaces in wsdl file
    xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/"
    xmlns:http="http://schemas.xmlsoap.org/wsdl/http/"
    xmlns:xsd="http://www.w3.org/2001/XMLSchema"
    Then change the Request msg from element type to string type like below
    <message name="UserLoggOffRequestMessage">
    <part name="UserId" type="xsd:string"/> (add this one))
    <!--<part name="payload" element="client:UserLoggOffProcessRequest"/>-->(remove this one)
    </message>
    Then change the binding
    <binding name="UserLoggOffBinding" type="client:UserLoggOff">
    <http:binding verb="GET"/>
    <operation name="process">
    <http:operation location="/process"/>
    <http:urlEncoded/>
    <output>
    <mime:mimeString part="Body"/>
    </output>
    </operation>
    </binding>
    Then do some changes in service tag . we need to do the changes in location only.
    we need to remove orabpel from location and add httpbinding
    http://infva04718.vshodc.lntinfotech.com:8888/*orabpel*/MobileApplication/UserLoggOff/1.0
    http://infva04718.vshodc.lntinfotech.com:8888/*httpbinding*/MobileApplication/UserLoggOff/1.0
    do like following
    <service name="UserLoggOff">
    <port name="UserLoggOffPort" binding="client:UserLoggOffBinding">
    <http:address location="http://infva04718.vshodc.lntinfotech.com:8888/httpbinding/MobileApplication/UserLoggOff/1.0"/>
    </port>
    </service>
    Then deploy the process then u can invoke this
    http://infva04718.vshodc.lntinfotech.com:8888/httpbinding/MobileApplication/UserLoggOff/process?UserId=a1
    here process is name of process u want to invoke

  • 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

  • Siebel says Invalid BPEL WSDL

    I have a WSDL created by BPEL and am trying to import it in Siebel. Siebel then throws errors. See below for errors and WSDL.
    Can anyone help?
    Siebel Errors:
    Errors during processing:
    There are no web service definitions to be generated.(SBL-EAI-04340)
    Following are warnings generated in the process:
    Service 'OutBoundDemoCallbackService' can not be imported, because none of its ports could be imported.(SBL-EAI-04333)
    Port 'OutBoundDemoCallbackPort' can not be imported. The binding element 'http://xmlns.oracle.com/OutBoundDemo:OutBoundDemoCallbackBinding' is invalid.
    (SBL-EAI-05153)
    .The SoapOperation %1 does not have either an input or output SoapBody child.
    Service 'OutBoundDemo' can not be imported, because none of its ports could be imported.(SBL-EAI-04333)
    Port 'OutBoundDemoPort' can not be imported. The binding element 'http://xmlns.oracle.com/OutBoundDemo:OutBoundDemoBinding' is invalid.
    (SBL-EAI-05153)
    .The SoapOperation %1 does not have either an input or output SoapBody child.
    BPEL WSDL
    <?xml version="1.0" encoding="UTF-8" ?>
    <definitions name="OutBoundDemo" targetNamespace="http://xmlns.oracle.com/OutBoundDemo" xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:tns="http://xmlns.oracle.com/OutBoundDemo" xmlns:wsa="http://schemas.xmlsoap.org/ws/2003/03/addressing" xmlns:ns1="http://www.siebel.com/xml/CSST%20Contact%20Interface" 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/OutBoundDemo">
    <types>
    <schema attributeFormDefault="qualified" elementFormDefault="qualified" targetNamespace="http://xmlns.oracle.com/OutBoundDemo" xmlns="http://www.w3.org/2001/XMLSchema" xmlns:client="http://xmlns.oracle.com/OutBoundDemo" xmlns:ns1="http://www.siebel.com/xml/CSST%20Contact%20Interface" xmlns:plnk="http://schemas.xmlsoap.org/ws/2003/05/partner-link/">
    <element name="OutBoundDemoProcessRequest">
    <complexType>
    <sequence>
    <element name="input" type="string" />
    </sequence>
    </complexType>
    </element>
    <element name="OutBoundDemoProcessResponse">
    <complexType>
    <sequence>
    <element name="result" type="string" />
    </sequence>
    </complexType>
    </element>
    </schema>
    <xsd:schema xmlns:client="http://xmlns.oracle.com/OutBoundDemo" xmlns:ns1="http://www.siebel.com/xml/CSST%20Contact%20Interface" xmlns:plnk="http://schemas.xmlsoap.org/ws/2003/05/partner-link/" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
    <xsd:import namespace="http://www.siebel.com/xml/CSST%20Contact%20Interface" schemaLocation="CSSTContactInterface.xsd" />
    </xsd:schema>
    <schema xmlns="http://www.w3.org/2001/XMLSchema">
    <import namespace="http://schemas.xmlsoap.org/ws/2003/03/addressing" schemaLocation="http://sgaur-us:9700/orabpel/xmllib/ws-addressing.xsd" />
    </schema>
    </types>
    <message name="WSAMessageIDHeader">
    <part name="MessageID" element="wsa:MessageID" />
    </message>
    <message name="OutBoundDemoRequestMessage">
    <part name="payload" element="ns1:SiebelMessage" />
    </message>
    <message name="WSAReplyToHeader">
    <part name="ReplyTo" element="wsa:ReplyTo" />
    </message>
    <message name="WSARelatesToHeader">
    <part name="RelatesTo" element="wsa:RelatesTo" />
    </message>
    <message name="OutBoundDemoResponseMessage">
    <part name="payload" element="tns:OutBoundDemoProcessResponse" />
    </message>
    <portType name="OutBoundDemoCallback">
    <operation name="onResult">
    <input message="tns:OutBoundDemoResponseMessage" />
    </operation>
    </portType>
    <portType name="OutBoundDemo">
    <operation name="initiate">
    <input message="tns:OutBoundDemoRequestMessage" />
    </operation>
    </portType>
    <binding name="OutBoundDemoCallbackBinding" type="tns:OutBoundDemoCallback">
    <soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http" />
    <operation name="onResult">
    <soap:operation style="document" soapAction="onResult" />
    <input>
    <soap:header message="tns:WSARelatesToHeader" part="RelatesTo" use="literal" encodingStyle="" />
    <soap:body use="literal" />
    </input>
    </operation>
    </binding>
    <binding name="OutBoundDemoBinding" type="tns:OutBoundDemo">
    <soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http" />
    <operation name="initiate">
    <soap:operation style="document" soapAction="initiate" />
    <input>
    <soap:header message="tns:WSAReplyToHeader" part="ReplyTo" use="literal" encodingStyle="" />
    <soap:header message="tns:WSAMessageIDHeader" part="MessageID" use="literal" encodingStyle="" />
    <soap:body use="literal" />
    </input>
    </operation>
    </binding>
    <service name="OutBoundDemoCallbackService">
    <port name="OutBoundDemoCallbackPort" binding="tns:OutBoundDemoCallbackBinding">
    <soap:address location="http://set.by.caller" />
    </port>
    </service>
    <service name="OutBoundDemo">
    <port name="OutBoundDemoPort" binding="tns:OutBoundDemoBinding">
    <soap:address location="http://sgaur-us:9700/orabpel/default/OutBoundDemo/1.0" />
    </port>
    </service>
    <plnk:partnerLinkType name="OutBoundDemo">
    <plnk:role name="OutBoundDemoProvider">
    <plnk:portType name="tns:OutBoundDemo" />
    </plnk:role>
    <plnk:role name="OutBoundDemoRequester">
    <plnk:portType name="tns:OutBoundDemoCallback" />
    </plnk:role>
    </plnk:partnerLinkType>
    </definitions>

    Edwin (or anyone else),
    We are also trying to invoke a BPEL process from Siebel and have read your advice in this thread.
    We can successful consume a Synchronous HelloWorld process from Siebel, but it is failing with consuming an Asynchronous HelloWorld from Siebel.
    This is a production project and while we are not concerned about callbacks with Siebel, it is not feasible to accept synchronous communications for this BPEL process as we cannot have Siebel waiting on completion - (HelloWorld is a cutdown use case produced to debug the issues we had with our real WSDL).
    Do you have any advice on how we can bridge the issues and produce an asynchronous process that can be consumed by Siebel ? Is this an issue with WSDL conformity - we are using Siebel 7.7? Is there an issue with regard to the way Siebel and Oracle PM handle WS-Addressing ?
    Mark.

  • Call Bpel process from JSP

    hi I am completely new to BPEL and supposed to call BPEL process frm JSP page....i went through a couple of tutorials and learnt about the Technology. But still couldnt find the way. Can any one help or send some link where i can download few sample application or Tell me the way to do this????

    The payload of the XML is described in the WSDL of the webservice. In general this is described in a XML schema (xsd). When you user selects a web service, you could read the WSDL of the webserice an determine the payload of this service, or you program this in you java code for each service.

  • How to call BPEL process in JSP page

    Hi
    I am new to BPEL.please help me how to call BPEL process in JSP page.
    Thank You...

    Check this thread ....
    How can i call asyncronous BPEL process from Java Class????
    Tom..

Maybe you are looking for