Direct Biding BPEL to OSB zombie

Hi guys,
We have a problem in company. We have some scenarios call services OSB in BPEL by direct binding, The OSB response normal, however the direct binding is zombie, and after some moments that is possible track in Enterprise Manager. This happens in several machines. Don't know what do. Someone Can I help ? Thanks.
Edited by: user9320747 on 27/05/2013 06:46

If the OSB service is responding properly, then you may have to tune your BPEL component. Set the properties like persistence property to faulted, in memory optimization..etc and check

Similar Messages

  • BPEL to OSB invocation using direct bindings

    Hi,
    Can we communicate from BPEL to OSB using direct bindings ?
    As per my understand in the document i have read it is given that from OSB to BPEL it can be communicated using SOA DIRECT protocol
    is my understand correct ?
    And can we achieve the same from BPEL to OSB call ?
    How can we achieve this ?
    regards
    Shankari

    In soa 11g,both ways are possible using direct binding:
    follow below blogs for both ways(soa to osb and osb to soa)
    http://www.xenta.nl/blog/2010/06/02/oracle-service-bus-11g-communication-with-oracle-soa-suite-11g-directbindings-part1/
    http://www.xenta.nl/blog/2010/06/06/oracle-service-bus-11g-communication-with-oracle-soa-suite-11g-directbindings-and-soa-direct-part2/

  • BPEL or OSB Integartion with ORACLE CEP

    Hi all,
    Can any body give me url or links or documents which will give me good idea on . How we can pass events from BPEL or OSB to CEP .
    Other wise how can issue the SOA 11g Event Delivery Network (EDN) with CEP .
    Any help appreciated.
    Thanks

    http://www.oracle.com/technology/sample_code/products/event-driven-architecture/index.html#11gR1
    http://download.oracle.com/docs/cd/E14571_01/doc.1111/e14301/toc.htm
    Regards,
    Anuj

  • Errors in direct binding invocation from BPEL to OSB

    Hi All,
    I have a problem in direct binding invocations between BPEL instances and OSB, this is the detail:
    There is in my composite a BPEL process that includes a catchAll component to manage all the faults resulting in the OSB invoke action and there is a fault policy too configured to manage the retry invocations. If the flow ends successfully there is no problem but if an error happens in the OSB part (time outs, bad address configuration in reference bindings details or something similar) the composite doesn't catch anything and retries aren't executed. The BPEL instance keeps in "running with errors" state from this moment.
    Any help about the management of this situation would be appreciated.
    Thanks,
    The log trace is the next one:
    [component_instance_id: 18440047] Failed to handle dispatch message ... exception ORABPEL-05002[[
    Message handle error.
    error while attempting to process the message "com.collaxa.cube.engine.dispatch.message.invoke.InvokeInstanceMessage"; the reported exception is: JTA transaction is not in active state.
    The transaction became inactive when executing activity "" for instance "18,440,048", bpel engine can not proceed further without an active transaction. please debug the invoked subsystem on why the transaction is not in active status. the transaction status is "MARKED_ROLLBACK".
    The reason was The execution of this instance "18440048" for process "ErrorBPELProcess1" is supposed to be in an active jta transaction, the current transaction status is "MARKED_ROLLBACK", the underlying exception is "oracle.soa.api.invocation.InvocationException: com.bea.wli.sb.transports.client.SBTransportException: An error occured while un-marshalling the request message: com.bea.alsb.ws.codec.CodecException: com.bea.alsb.ws.codec.CodecException: The SOAP envelope is not formatted according to the RPC style. The SOAP Body tag must have one and only one child element (named after the operation name).
    com.bea.alsb.ws.codec.CodecException: com.bea.alsb.ws.codec.CodecException: The SOAP envelope is not formatted according to the RPC style. The SOAP Body tag must have one and only one child element (named after the operation name).
         at com.bea.alsb.soa.codec.SOACodecUtil.unmarshall(SOACodecUtil.java:163)
         at com.bea.wli.sb.transports.sb.codec.SOAMessageHandler.createResponse(SOAMessageHandler.java:116)
         at com.bea.wli.sb.transports.sb.bean.SBDispatcherBean.invoke(SBDispatcherBean.java:355)
         at com.bea.wli.sb.transports.sb.bean.SBDispatcher_nwlqik_EOImpl.__WL_invoke(Unknown Source)
         at weblogic.ejb.container.internal.SessionRemoteMethodInvoker.invoke(SessionRemoteMethodInvoker.java:40)
         at com.bea.wli.sb.transports.sb.bean.SBDispatcher_nwlqik_EOImpl.invoke(Unknown Source)
         at com.bea.wli.sb.transports.sb.bean.SBDispatcher_nwlqik_EOImpl_WLSkel.invoke(Unknown Source)
         at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:667)
         at weblogic.rmi.cluster.ClusterableServerRef.invoke(ClusterableServerRef.java:230)
         at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:522)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:146)
         at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:518)
         at weblogic.rmi.internal.wls.WLSExecuteRequest.run(WLSExecuteRequest.java:118)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
    Caused by: com.bea.alsb.ws.codec.CodecException: The SOAP envelope is not formatted according to the RPC style. The SOAP Body tag must have one and only one child element (named after the operation name).
         at com.bea.alsb.ws.codec.internal.runtime.soap.SoapRpcCodec.unmarshallBody(SoapRpcCodec.java:107)
         at com.bea.alsb.ws.codec.internal.runtime.soap.SoapCodec.unmarshall(SoapCodec.java:262)
         at com.bea.alsb.ws.codec.internal.runtime.soap.SoapRpcServiceCodec.unmarshall(SoapRpcServiceCodec.java:60)
         at com.bea.alsb.soa.codec.SOACodecUtil.unmarshall(SOACodecUtil.java:155)
         ... 15 more
    Consult the system administrator regarding this error.
    This error contained an exception thrown by the message handler.
    Check the exception trace in the log (with logging level set to debug mode).
    ORABPEL-05002
    Message handle error.
    error while attempting to process the message "com.collaxa.cube.engine.dispatch.message.invoke.InvokeInstanceMessage"; the reported exception is: JTA transaction is not in active state.
    The transaction became inactive when executing activity "" for instance "18,440,048", bpel engine can not proceed further without an active transaction. please debug the invoked subsystem on why the transaction is not in active status. the transaction status is "MARKED_ROLLBACK".
    The reason was The execution of this instance "18440048" for process "ErrorBPELProcess1" is supposed to be in an active jta transaction, the current transaction status is "MARKED_ROLLBACK", the underlying exception is "oracle.soa.api.invocation.InvocationException: com.bea.wli.sb.transports.client.SBTransportException: An error occured while un-marshalling the request message: com.bea.alsb.ws.codec.CodecException: com.bea.alsb.ws.codec.CodecException: The SOAP envelope is not formatted according to the RPC style. The SOAP Body tag must have one and only one child element (named after the operation name).
    com.bea.alsb.ws.codec.CodecException: com.bea.alsb.ws.codec.CodecException: The SOAP envelope is not formatted according to the RPC style. The SOAP Body tag must have one and only one child element (named after the operation name).
         at com.bea.alsb.soa.codec.SOACodecUtil.unmarshall(SOACodecUtil.java:163)
         at com.bea.wli.sb.transports.sb.codec.SOAMessageHandler.createResponse(SOAMessageHandler.java:116)
         at com.bea.wli.sb.transports.sb.bean.SBDispatcherBean.invoke(SBDispatcherBean.java:355)
         at com.bea.wli.sb.transports.sb.bean.SBDispatcher_nwlqik_EOImpl.__WL_invoke(Unknown Source)
         at weblogic.ejb.container.internal.SessionRemoteMethodInvoker.invoke(SessionRemoteMethodInvoker.java:40)
         at com.bea.wli.sb.transports.sb.bean.SBDispatcher_nwlqik_EOImpl.invoke(Unknown Source)
         at com.bea.wli.sb.transports.sb.bean.SBDispatcher_nwlqik_EOImpl_WLSkel.invoke(Unknown Source)
         at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:667)
         at weblogic.rmi.cluster.ClusterableServerRef.invoke(ClusterableServerRef.java:230)
         at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:522)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:146)
         at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:518)
         at weblogic.rmi.internal.wls.WLSExecuteRequest.run(WLSExecuteRequest.java:118)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
    Caused by: com.bea.alsb.ws.codec.CodecException: The SOAP envelope is not formatted according to the RPC style. The SOAP Body tag must have one and only one child element (named after the operation name).
         at com.bea.alsb.ws.codec.internal.runtime.soap.SoapRpcCodec.unmarshallBody(SoapRpcCodec.java:107)
         at com.bea.alsb.ws.codec.internal.runtime.soap.SoapCodec.unmarshall(SoapCodec.java:262)
         at com.bea.alsb.ws.codec.internal.runtime.soap.SoapRpcServiceCodec.unmarshall(SoapRpcServiceCodec.java:60)
         at com.bea.alsb.soa.codec.SOACodecUtil.unmarshall(SOACodecUtil.java:155)
         ... 15 more
    Consult the system administrator regarding this error.
    This error contained an exception thrown by the message handler.
    Check the exception trace in the log (with logging level set to debug mode).
         at com.collaxa.cube.engine.dispatch.DispatchHelper.handleMessage(DispatchHelper.java:205)
         at com.collaxa.cube.engine.dispatch.BaseDispatchTask.process(BaseDispatchTask.java:88)
         at com.collaxa.cube.engine.dispatch.BaseDispatchTask.run(BaseDispatchTask.java:64)
         at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
         at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
         at com.collaxa.cube.engine.dispatch.Dispatcher$ContextCapturingThreadFactory$2.run(Dispatcher.java:850)
         at java.lang.Thread.run(Thread.java:662)
    And this is the payload from the instance details:
    <messages>
    <input>
    ... input data....
    </input>
    <fault>
    <exception class="com.collaxa.cube.engine.EngineException">
    JTA transaction is not in active state. The transaction became inactive when executing activity "" for instance "18,440,048", bpel engine can not proceed further without an active transaction. please debug the invoked subsystem on why the transaction is not in active status. the transaction status is "MARKED_ROLLBACK". The reason was The execution of this instance "18440048" for process "ErrorBPELProcess1" is supposed to be in an active jta transaction, the current transaction status is "MARKED_ROLLBACK", the underlying exception is "oracle.soa.api.invocation.InvocationException: com.bea.wli.sb.transports.client.SBTransportException: An error occured while un-marshalling the request message: com.bea.alsb.ws.codec.CodecException: com.bea.alsb.ws.codec.CodecException: The SOAP envelope is not formatted according to the RPC style. The SOAP Body tag must have one and only one child element (named after the operation name). com.bea.alsb.ws.codec.CodecException: com.bea.alsb.ws.codec.CodecException: The SOAP envelope is not formatted according to the RPC style. The SOAP Body tag must have one and only one child element (named after the operation name). at com.bea.alsb.soa.codec.SOACodecUtil.unmarshall(SOACodecUtil.java:163) at com.bea.wli.sb.transports.sb.codec.SOAMessageHandler.createResponse(SOAMessageHandler.java:116) at com.bea.wli.sb.transports.sb.bean.SBDispatcherBean.invoke(SBDispatcherBean.java:355) at com.bea.wli.sb.transports.sb.bean.SBDispatcher_nwlqik_EOImpl.__WL_invoke(Unknown Source) at weblogic.ejb.container.internal.SessionRemoteMethodInvoker.invoke(SessionRemoteMethodInvoker.java:40) at com.bea.wli.sb.transports.sb.bean.SBDispatcher_nwlqik_EOImpl.invoke(Unknown Source) at com.bea.wli.sb.transports.sb.bean.SBDispatcher_nwlqik_EOImpl_WLSkel.invoke(Unknown Source) at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:667) at weblogic.rmi.cluster.ClusterableServerRef.invoke(ClusterableServerRef.java:230) at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:522) at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363) at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:146) at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:518) at weblogic.rmi.internal.wls.WLSExecuteRequest.run(WLSExecuteRequest.java:118) at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256) at weblogic.work.ExecuteThread.run(ExecuteThread.java:221) Caused by: com.bea.alsb.ws.codec.CodecException: The SOAP envelope is not formatted according to the RPC style. The SOAP Body tag must have one and only one child element (named after the operation name). at com.bea.alsb.ws.codec.internal.runtime.soap.SoapRpcCodec.unmarshallBody(SoapRpcCodec.java:107) at com.bea.alsb.ws.codec.internal.runtime.soap.SoapCodec.unmarshall(SoapCodec.java:262) at com.bea.alsb.ws.codec.internal.runtime.soap.SoapRpcServiceCodec.unmarshall(SoapRpcServiceCodec.java:60) at com.bea.alsb.soa.codec.SOACodecUtil.unmarshall(SOACodecUtil.java:155) ... 15 more " . Consult the system administrator regarding this error.
    <stack>
    <f>com.oracle.bpel.client.util.TransactionUtils.throwExceptionIfTxnNotActive#107</f>
    <f>com.collaxa.cube.ws.WSInvocationManager.invoke#352</f>
    <f>com.collaxa.cube.engine.ext.common.InvokeHandler.__invoke#1070</f>
    <f>com.collaxa.cube.engine.ext.common.InvokeHandler.handleNormalInvoke#584</f>
    <f>com.collaxa.cube.engine.ext.common.InvokeHandler.handle#132</f>
    <f>com.collaxa.cube.engine.ext.bpel.common.wmp.BPELInvokeWMP.__executeStatements#74</f>
    <f>com.collaxa.cube.engine.ext.bpel.common.wmp.BaseBPELActivityWMP.perform#166</f>
    <f>com.collaxa.cube.engine.CubeEngine.performActivity#2687</f>
    <f>com.collaxa.cube.engine.CubeEngine._handleWorkItem#1190</f>
    <f>com.collaxa.cube.engine.CubeEngine.handleWorkItem#1093</f>
    <f>com.collaxa.cube.engine.dispatch.message.instance.PerformMessageHandler.handleLocal#76</f>
    <f>com.collaxa.cube.engine.dispatch.DispatchHelper.handleLocalMessage#218</f>
    <f>com.collaxa.cube.engine.dispatch.DispatchHelper.sendMemory#297</f>
    <f>com.collaxa.cube.engine.CubeEngine.endRequest#4609</f>
    <f>com.collaxa.cube.engine.CubeEngine.endRequest#4540</f>
    <f>com.collaxa.cube.engine.CubeEngine._createAndInvoke#713</f>
    <f>...</f>
    </stack>
    </exception>
    <root class="oracle.fabric.common.FabricInvocationException">
    oracle.soa.api.invocation.InvocationException: com.bea.wli.sb.transports.client.SBTransportException: An error occured while un-marshalling the request message: com.bea.alsb.ws.codec.CodecException: com.bea.alsb.ws.codec.CodecException: The SOAP envelope is not formatted according to the RPC style. The SOAP Body tag must have one and only one child element (named after the operation name). com.bea.alsb.ws.codec.CodecException: com.bea.alsb.ws.codec.CodecException: The SOAP envelope is not formatted according to the RPC style. The SOAP Body tag must have one and only one child element (named after the operation name). at com.bea.alsb.soa.codec.SOACodecUtil.unmarshall(SOACodecUtil.java:163) at com.bea.wli.sb.transports.sb.codec.SOAMessageHandler.createResponse(SOAMessageHandler.java:116) at com.bea.wli.sb.transports.sb.bean.SBDispatcherBean.invoke(SBDispatcherBean.java:355) at com.bea.wli.sb.transports.sb.bean.SBDispatcher_nwlqik_EOImpl.__WL_invoke(Unknown Source) at weblogic.ejb.container.internal.SessionRemoteMethodInvoker.invoke(SessionRemoteMethodInvoker.java:40) at com.bea.wli.sb.transports.sb.bean.SBDispatcher_nwlqik_EOImpl.invoke(Unknown Source) at com.bea.wli.sb.transports.sb.bean.SBDispatcher_nwlqik_EOImpl_WLSkel.invoke(Unknown Source) at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:667) at weblogic.rmi.cluster.ClusterableServerRef.invoke(ClusterableServerRef.java:230) at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:522) at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363) at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:146) at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:518) at weblogic.rmi.internal.wls.WLSExecuteRequest.run(WLSExecuteRequest.java:118) at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256) at weblogic.work.ExecuteThread.run(ExecuteThread.java:221) Caused by: com.bea.alsb.ws.codec.CodecException: The SOAP envelope is not formatted according to the RPC style. The SOAP Body tag must have one and only one child element (named after the operation name). at com.bea.alsb.ws.codec.internal.runtime.soap.SoapRpcCodec.unmarshallBody(SoapRpcCodec.java:107) at com.bea.alsb.ws.codec.internal.runtime.soap.SoapCodec.unmarshall(SoapCodec.java:262) at com.bea.alsb.ws.codec.internal.runtime.soap.SoapRpcServiceCodec.unmarshall(SoapRpcServiceCodec.java:60) at com.bea.alsb.soa.codec.SOACodecUtil.unmarshall(SOACodecUtil.java:155) ... 15 more
    <stack>
    <f>oracle.integration.platform.blocks.direct.OutboundMessageDispatcher.request#124</f>
    <f>oracle.integration.platform.blocks.direct.DirectExternalBindingComponent.request#190</f>
    <f>oracle.integration.platform.blocks.mesh.SynchronousMessageHandler.doRequest#139</f>
    <f>oracle.integration.platform.blocks.mesh.MessageRouter.request#182</f>
    <f>oracle.integration.platform.blocks.mesh.MeshImpl$2.run#178</f>
    <f>java.security.AccessController.doPrivileged</f>
    <f>javax.security.auth.Subject.doAs#396</f>
    <f>oracle.integration.platform.blocks.mesh.MeshImpl.doRequestAsSubject#176</f>
    <f>oracle.integration.platform.blocks.mesh.MeshImpl.request#151</f>
    <f>sun.reflect.GeneratedMethodAccessor1294.invoke</f>
    <f>sun.reflect.DelegatingMethodAccessorImpl.invoke#25</f>
    <f>java.lang.reflect.Method.invoke#597</f>
    <f>org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection#307</f>
    <f>org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint#182</f>
    <f>org.springframework.aop.framework.ReflectiveMethodInvocation.proceed#149</f>
    <f>oracle.integration.platform.metrics.PhaseEventAspect.invoke#71</f>
    <f>...</f>
    </stack>
    </root>
    </fault>
    </messages>
    Edited by: luismi fernandez on Aug 1, 2012 1:20 AM

    Hi All,
    I have a problem in direct binding invocations between BPEL instances and OSB, this is the detail:
    There is in my composite a BPEL process that includes a catchAll component to manage all the faults resulting in the OSB invoke action and there is a fault policy too configured to manage the retry invocations. If the flow ends successfully there is no problem but if an error happens in the OSB part (time outs, bad address configuration in reference bindings details or something similar) the composite doesn't catch anything and retries aren't executed. The BPEL instance keeps in "running with errors" state from this moment.
    Any help about the management of this situation would be appreciated.
    Thanks,
    The log trace is the next one:
    [component_instance_id: 18440047] Failed to handle dispatch message ... exception ORABPEL-05002[[
    Message handle error.
    error while attempting to process the message "com.collaxa.cube.engine.dispatch.message.invoke.InvokeInstanceMessage"; the reported exception is: JTA transaction is not in active state.
    The transaction became inactive when executing activity "" for instance "18,440,048", bpel engine can not proceed further without an active transaction. please debug the invoked subsystem on why the transaction is not in active status. the transaction status is "MARKED_ROLLBACK".
    The reason was The execution of this instance "18440048" for process "ErrorBPELProcess1" is supposed to be in an active jta transaction, the current transaction status is "MARKED_ROLLBACK", the underlying exception is "oracle.soa.api.invocation.InvocationException: com.bea.wli.sb.transports.client.SBTransportException: An error occured while un-marshalling the request message: com.bea.alsb.ws.codec.CodecException: com.bea.alsb.ws.codec.CodecException: The SOAP envelope is not formatted according to the RPC style. The SOAP Body tag must have one and only one child element (named after the operation name).
    com.bea.alsb.ws.codec.CodecException: com.bea.alsb.ws.codec.CodecException: The SOAP envelope is not formatted according to the RPC style. The SOAP Body tag must have one and only one child element (named after the operation name).
         at com.bea.alsb.soa.codec.SOACodecUtil.unmarshall(SOACodecUtil.java:163)
         at com.bea.wli.sb.transports.sb.codec.SOAMessageHandler.createResponse(SOAMessageHandler.java:116)
         at com.bea.wli.sb.transports.sb.bean.SBDispatcherBean.invoke(SBDispatcherBean.java:355)
         at com.bea.wli.sb.transports.sb.bean.SBDispatcher_nwlqik_EOImpl.__WL_invoke(Unknown Source)
         at weblogic.ejb.container.internal.SessionRemoteMethodInvoker.invoke(SessionRemoteMethodInvoker.java:40)
         at com.bea.wli.sb.transports.sb.bean.SBDispatcher_nwlqik_EOImpl.invoke(Unknown Source)
         at com.bea.wli.sb.transports.sb.bean.SBDispatcher_nwlqik_EOImpl_WLSkel.invoke(Unknown Source)
         at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:667)
         at weblogic.rmi.cluster.ClusterableServerRef.invoke(ClusterableServerRef.java:230)
         at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:522)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:146)
         at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:518)
         at weblogic.rmi.internal.wls.WLSExecuteRequest.run(WLSExecuteRequest.java:118)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
    Caused by: com.bea.alsb.ws.codec.CodecException: The SOAP envelope is not formatted according to the RPC style. The SOAP Body tag must have one and only one child element (named after the operation name).
         at com.bea.alsb.ws.codec.internal.runtime.soap.SoapRpcCodec.unmarshallBody(SoapRpcCodec.java:107)
         at com.bea.alsb.ws.codec.internal.runtime.soap.SoapCodec.unmarshall(SoapCodec.java:262)
         at com.bea.alsb.ws.codec.internal.runtime.soap.SoapRpcServiceCodec.unmarshall(SoapRpcServiceCodec.java:60)
         at com.bea.alsb.soa.codec.SOACodecUtil.unmarshall(SOACodecUtil.java:155)
         ... 15 more
    Consult the system administrator regarding this error.
    This error contained an exception thrown by the message handler.
    Check the exception trace in the log (with logging level set to debug mode).
    ORABPEL-05002
    Message handle error.
    error while attempting to process the message "com.collaxa.cube.engine.dispatch.message.invoke.InvokeInstanceMessage"; the reported exception is: JTA transaction is not in active state.
    The transaction became inactive when executing activity "" for instance "18,440,048", bpel engine can not proceed further without an active transaction. please debug the invoked subsystem on why the transaction is not in active status. the transaction status is "MARKED_ROLLBACK".
    The reason was The execution of this instance "18440048" for process "ErrorBPELProcess1" is supposed to be in an active jta transaction, the current transaction status is "MARKED_ROLLBACK", the underlying exception is "oracle.soa.api.invocation.InvocationException: com.bea.wli.sb.transports.client.SBTransportException: An error occured while un-marshalling the request message: com.bea.alsb.ws.codec.CodecException: com.bea.alsb.ws.codec.CodecException: The SOAP envelope is not formatted according to the RPC style. The SOAP Body tag must have one and only one child element (named after the operation name).
    com.bea.alsb.ws.codec.CodecException: com.bea.alsb.ws.codec.CodecException: The SOAP envelope is not formatted according to the RPC style. The SOAP Body tag must have one and only one child element (named after the operation name).
         at com.bea.alsb.soa.codec.SOACodecUtil.unmarshall(SOACodecUtil.java:163)
         at com.bea.wli.sb.transports.sb.codec.SOAMessageHandler.createResponse(SOAMessageHandler.java:116)
         at com.bea.wli.sb.transports.sb.bean.SBDispatcherBean.invoke(SBDispatcherBean.java:355)
         at com.bea.wli.sb.transports.sb.bean.SBDispatcher_nwlqik_EOImpl.__WL_invoke(Unknown Source)
         at weblogic.ejb.container.internal.SessionRemoteMethodInvoker.invoke(SessionRemoteMethodInvoker.java:40)
         at com.bea.wli.sb.transports.sb.bean.SBDispatcher_nwlqik_EOImpl.invoke(Unknown Source)
         at com.bea.wli.sb.transports.sb.bean.SBDispatcher_nwlqik_EOImpl_WLSkel.invoke(Unknown Source)
         at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:667)
         at weblogic.rmi.cluster.ClusterableServerRef.invoke(ClusterableServerRef.java:230)
         at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:522)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:146)
         at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:518)
         at weblogic.rmi.internal.wls.WLSExecuteRequest.run(WLSExecuteRequest.java:118)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
    Caused by: com.bea.alsb.ws.codec.CodecException: The SOAP envelope is not formatted according to the RPC style. The SOAP Body tag must have one and only one child element (named after the operation name).
         at com.bea.alsb.ws.codec.internal.runtime.soap.SoapRpcCodec.unmarshallBody(SoapRpcCodec.java:107)
         at com.bea.alsb.ws.codec.internal.runtime.soap.SoapCodec.unmarshall(SoapCodec.java:262)
         at com.bea.alsb.ws.codec.internal.runtime.soap.SoapRpcServiceCodec.unmarshall(SoapRpcServiceCodec.java:60)
         at com.bea.alsb.soa.codec.SOACodecUtil.unmarshall(SOACodecUtil.java:155)
         ... 15 more
    Consult the system administrator regarding this error.
    This error contained an exception thrown by the message handler.
    Check the exception trace in the log (with logging level set to debug mode).
         at com.collaxa.cube.engine.dispatch.DispatchHelper.handleMessage(DispatchHelper.java:205)
         at com.collaxa.cube.engine.dispatch.BaseDispatchTask.process(BaseDispatchTask.java:88)
         at com.collaxa.cube.engine.dispatch.BaseDispatchTask.run(BaseDispatchTask.java:64)
         at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
         at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
         at com.collaxa.cube.engine.dispatch.Dispatcher$ContextCapturingThreadFactory$2.run(Dispatcher.java:850)
         at java.lang.Thread.run(Thread.java:662)
    And this is the payload from the instance details:
    <messages>
    <input>
    ... input data....
    </input>
    <fault>
    <exception class="com.collaxa.cube.engine.EngineException">
    JTA transaction is not in active state. The transaction became inactive when executing activity "" for instance "18,440,048", bpel engine can not proceed further without an active transaction. please debug the invoked subsystem on why the transaction is not in active status. the transaction status is "MARKED_ROLLBACK". The reason was The execution of this instance "18440048" for process "ErrorBPELProcess1" is supposed to be in an active jta transaction, the current transaction status is "MARKED_ROLLBACK", the underlying exception is "oracle.soa.api.invocation.InvocationException: com.bea.wli.sb.transports.client.SBTransportException: An error occured while un-marshalling the request message: com.bea.alsb.ws.codec.CodecException: com.bea.alsb.ws.codec.CodecException: The SOAP envelope is not formatted according to the RPC style. The SOAP Body tag must have one and only one child element (named after the operation name). com.bea.alsb.ws.codec.CodecException: com.bea.alsb.ws.codec.CodecException: The SOAP envelope is not formatted according to the RPC style. The SOAP Body tag must have one and only one child element (named after the operation name). at com.bea.alsb.soa.codec.SOACodecUtil.unmarshall(SOACodecUtil.java:163) at com.bea.wli.sb.transports.sb.codec.SOAMessageHandler.createResponse(SOAMessageHandler.java:116) at com.bea.wli.sb.transports.sb.bean.SBDispatcherBean.invoke(SBDispatcherBean.java:355) at com.bea.wli.sb.transports.sb.bean.SBDispatcher_nwlqik_EOImpl.__WL_invoke(Unknown Source) at weblogic.ejb.container.internal.SessionRemoteMethodInvoker.invoke(SessionRemoteMethodInvoker.java:40) at com.bea.wli.sb.transports.sb.bean.SBDispatcher_nwlqik_EOImpl.invoke(Unknown Source) at com.bea.wli.sb.transports.sb.bean.SBDispatcher_nwlqik_EOImpl_WLSkel.invoke(Unknown Source) at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:667) at weblogic.rmi.cluster.ClusterableServerRef.invoke(ClusterableServerRef.java:230) at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:522) at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363) at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:146) at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:518) at weblogic.rmi.internal.wls.WLSExecuteRequest.run(WLSExecuteRequest.java:118) at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256) at weblogic.work.ExecuteThread.run(ExecuteThread.java:221) Caused by: com.bea.alsb.ws.codec.CodecException: The SOAP envelope is not formatted according to the RPC style. The SOAP Body tag must have one and only one child element (named after the operation name). at com.bea.alsb.ws.codec.internal.runtime.soap.SoapRpcCodec.unmarshallBody(SoapRpcCodec.java:107) at com.bea.alsb.ws.codec.internal.runtime.soap.SoapCodec.unmarshall(SoapCodec.java:262) at com.bea.alsb.ws.codec.internal.runtime.soap.SoapRpcServiceCodec.unmarshall(SoapRpcServiceCodec.java:60) at com.bea.alsb.soa.codec.SOACodecUtil.unmarshall(SOACodecUtil.java:155) ... 15 more " . Consult the system administrator regarding this error.
    <stack>
    <f>com.oracle.bpel.client.util.TransactionUtils.throwExceptionIfTxnNotActive#107</f>
    <f>com.collaxa.cube.ws.WSInvocationManager.invoke#352</f>
    <f>com.collaxa.cube.engine.ext.common.InvokeHandler.__invoke#1070</f>
    <f>com.collaxa.cube.engine.ext.common.InvokeHandler.handleNormalInvoke#584</f>
    <f>com.collaxa.cube.engine.ext.common.InvokeHandler.handle#132</f>
    <f>com.collaxa.cube.engine.ext.bpel.common.wmp.BPELInvokeWMP.__executeStatements#74</f>
    <f>com.collaxa.cube.engine.ext.bpel.common.wmp.BaseBPELActivityWMP.perform#166</f>
    <f>com.collaxa.cube.engine.CubeEngine.performActivity#2687</f>
    <f>com.collaxa.cube.engine.CubeEngine._handleWorkItem#1190</f>
    <f>com.collaxa.cube.engine.CubeEngine.handleWorkItem#1093</f>
    <f>com.collaxa.cube.engine.dispatch.message.instance.PerformMessageHandler.handleLocal#76</f>
    <f>com.collaxa.cube.engine.dispatch.DispatchHelper.handleLocalMessage#218</f>
    <f>com.collaxa.cube.engine.dispatch.DispatchHelper.sendMemory#297</f>
    <f>com.collaxa.cube.engine.CubeEngine.endRequest#4609</f>
    <f>com.collaxa.cube.engine.CubeEngine.endRequest#4540</f>
    <f>com.collaxa.cube.engine.CubeEngine._createAndInvoke#713</f>
    <f>...</f>
    </stack>
    </exception>
    <root class="oracle.fabric.common.FabricInvocationException">
    oracle.soa.api.invocation.InvocationException: com.bea.wli.sb.transports.client.SBTransportException: An error occured while un-marshalling the request message: com.bea.alsb.ws.codec.CodecException: com.bea.alsb.ws.codec.CodecException: The SOAP envelope is not formatted according to the RPC style. The SOAP Body tag must have one and only one child element (named after the operation name). com.bea.alsb.ws.codec.CodecException: com.bea.alsb.ws.codec.CodecException: The SOAP envelope is not formatted according to the RPC style. The SOAP Body tag must have one and only one child element (named after the operation name). at com.bea.alsb.soa.codec.SOACodecUtil.unmarshall(SOACodecUtil.java:163) at com.bea.wli.sb.transports.sb.codec.SOAMessageHandler.createResponse(SOAMessageHandler.java:116) at com.bea.wli.sb.transports.sb.bean.SBDispatcherBean.invoke(SBDispatcherBean.java:355) at com.bea.wli.sb.transports.sb.bean.SBDispatcher_nwlqik_EOImpl.__WL_invoke(Unknown Source) at weblogic.ejb.container.internal.SessionRemoteMethodInvoker.invoke(SessionRemoteMethodInvoker.java:40) at com.bea.wli.sb.transports.sb.bean.SBDispatcher_nwlqik_EOImpl.invoke(Unknown Source) at com.bea.wli.sb.transports.sb.bean.SBDispatcher_nwlqik_EOImpl_WLSkel.invoke(Unknown Source) at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:667) at weblogic.rmi.cluster.ClusterableServerRef.invoke(ClusterableServerRef.java:230) at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:522) at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363) at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:146) at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:518) at weblogic.rmi.internal.wls.WLSExecuteRequest.run(WLSExecuteRequest.java:118) at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256) at weblogic.work.ExecuteThread.run(ExecuteThread.java:221) Caused by: com.bea.alsb.ws.codec.CodecException: The SOAP envelope is not formatted according to the RPC style. The SOAP Body tag must have one and only one child element (named after the operation name). at com.bea.alsb.ws.codec.internal.runtime.soap.SoapRpcCodec.unmarshallBody(SoapRpcCodec.java:107) at com.bea.alsb.ws.codec.internal.runtime.soap.SoapCodec.unmarshall(SoapCodec.java:262) at com.bea.alsb.ws.codec.internal.runtime.soap.SoapRpcServiceCodec.unmarshall(SoapRpcServiceCodec.java:60) at com.bea.alsb.soa.codec.SOACodecUtil.unmarshall(SOACodecUtil.java:155) ... 15 more
    <stack>
    <f>oracle.integration.platform.blocks.direct.OutboundMessageDispatcher.request#124</f>
    <f>oracle.integration.platform.blocks.direct.DirectExternalBindingComponent.request#190</f>
    <f>oracle.integration.platform.blocks.mesh.SynchronousMessageHandler.doRequest#139</f>
    <f>oracle.integration.platform.blocks.mesh.MessageRouter.request#182</f>
    <f>oracle.integration.platform.blocks.mesh.MeshImpl$2.run#178</f>
    <f>java.security.AccessController.doPrivileged</f>
    <f>javax.security.auth.Subject.doAs#396</f>
    <f>oracle.integration.platform.blocks.mesh.MeshImpl.doRequestAsSubject#176</f>
    <f>oracle.integration.platform.blocks.mesh.MeshImpl.request#151</f>
    <f>sun.reflect.GeneratedMethodAccessor1294.invoke</f>
    <f>sun.reflect.DelegatingMethodAccessorImpl.invoke#25</f>
    <f>java.lang.reflect.Method.invoke#597</f>
    <f>org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection#307</f>
    <f>org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint#182</f>
    <f>org.springframework.aop.framework.ReflectiveMethodInvocation.proceed#149</f>
    <f>oracle.integration.platform.metrics.PhaseEventAspect.invoke#71</f>
    <f>...</f>
    </stack>
    </root>
    </fault>
    </messages>
    Edited by: luismi fernandez on Aug 1, 2012 1:20 AM

  • XSLT and XQuery recommendation for BPEL and OSB

    Hi,
    1. Why is XQuery recommeded for OSB and XSLT for BPEL. Are there any specific performance optimization reason behind this.
    2. Apart from OSB and BPEL, both XSLT and XQuery has xml transformation options and creating HTML. What is the difference between these two.
    Thanks in advance!

    you can create the graphical view of Xquery in Eclipse but not for XSLT
    Xquery is much faster than XSLT in OSB.
    Through XSLT however you can achieve more complex transformation.
    OSB has its historic origins in BEA Aqalogic stable and so Xquery was widely used used even though XSLT is supported. It is a matter of choice(your standards in your organization,your developer skillsets,your re-usable libraries etc )
    In Jdeveloper you can develop xslt in graphical mode though and attain complex transformation

  • How to get the instance id of BPEL in OSB

    We have the process in OSB which will invoke the BPEL ansync process and returns success once the BPEL is invoked.
    Can we refer/get the BPEL instance id in OSB by anymeans?

    There is another option. You may set the unique instance name in BPEL process based on some value in the payload. From OSB you may query composite_instance table of SOAINFRA schema on the basis of instance name (title column) and/or composite name (composite_dn column) to get the value of instance id (ID column) and return it in response from OSB.
    Regards,
    Anuj

  • BPEL or OSB consume external webservices

    Hello all ,
    After I look over documentation and - Getting Started With Oracle SOA Suite 11g R1: A Hands-On Tutorial: Fast-Track Your SOA Adoption: Build a Service-Oriented Composite Application in Just Hours - still is not clear how can I consume a web-service hosted on other system - for example Websphere or SharePoint .
    I had a example one web service register
    <service name="DonateBeanService">
    <port binding="tns:DonateBeanPortBinding" name="DonateBeanPort">
    <soap:address location="http://localhost:8888/TestTopDown/services/DonateBeanPort"/>
    </port>
    </service>
    on my WAS CEE server .
    When I tried to made a business service in OSB - I imported the wsdl - create a new business service -add monitor capabilities but the call is not made to the service endpoint .
    Also inside BPEL how can I invoke a external webservice .
    Can anyone help me please with some points or advices ? What is wrong in the approach ? In the end OSB capabilities should allow me to integrate with other systems very easy .
    Many thanks in advance for all .
    And a HAPPY NEW YEAR .
    Best regards,
    Stefan

    how can invoke from inside a BPEL the same service ? or in the BPEL is better to have only local web-services BPEL can also invoke the same service. To know more about BPEL, please refer -
    http://www.oracle.com/technetwork/middleware/bpel/overview/index-088867.html
    Post BPEL related questions in BPEL forum -
    BPEL
    And the last one - if I need to read information from a file and send parameters to this webservice - how I will do it on the OSB ?Create a messaging type/Any XML proxy service in OSB with FILE/FTP transport (as per your requirement). In message flow of proxy service you may use XQuery/XSLT/MFL to transform the content of the pulled file into the XML required for calling web-service. Use communication actions to call business service from proxy service message flow. You may like to refer -
    http://download.oracle.com/docs/cd/E14571_01/doc.1111/e15866/toc.htm
    Regards,
    Anuj

  • Oracle Workflow - Statement of Direction and BPEL

    Hi,
    I am starting to study Oracle BPEL and other people at my company are studying Oracle Workflow.
    Recently I found the following article at the OTN, regarding the Statement of Direction of Oracle Workflow:
    http://www.oracle.com/technology/products/ias/workflow/workflow_sod.html
    It finishes saying:
    "As Oracle BPEL Process Manager provides out-of-the-box features for building human-based workflows, rules-based process automation, and integration style business processes, further development on OW4J will not continue and OW4J will not be released.
    Any new or existing customers who wish to build business processes in the middle tier are recommended to use Oracle BPEL Process Manager."
    So my question is: Does Oracle BPEL provides (or will provide) all the functionality implemented in Oracle Workflow ? If not what are the main differences ?
    I will be waiting for your thoughts
    Thanks,
    Claudio.

    Site mentioned above is an internal site. External site is http://otn.oracle.com/bpel
    I think the above highlighted SOD is about Oracle initiative to re-write current pl/sql based Workflow engine in Java so that it can ported to middle-tier. Since the acuisition of Collaxa they seems to be dumped that idea and positioning Oracle BPEL as the middle-tier process orchestration (BPM) solution.
    Having said that let me take a shot at comparing Oracle Workflow and BPEL products....
    Oracle Workflow
    * No way getting dropped as Oracle EBS has huge investments in it
    * Oracle Fusion Applications has plans to use the Oracle Workflow BES functionality extensively
    * Good for modeling business processes within a single DB/application instances. It's possible to integrate with external apps but not an elegant solution
    * Web Services can be a functional activity with in the work flow but again not an elegant solution. Requires DB java, queues and a listener
    * Doensn't provide sophisticated modeling artifacts like TaskManager, Faults, sensors etc out of the box. It's possible to build your own library.
    * Better performanent if the entire process interaction is within a single instance like Oracle EBS account generators, approval flows etc.
    * Based on proprietary technology
    Oracle BPEL
    * Based on standards like BPEL, WSDL and WSIF
    * What ever you can do in workflow can be done in BPEL but not the otherway round
    * Has adapters to interact with various transports like JDBC, AQ, JMS, JCA, HTTP. That means integration with existing workflows is very easy
    * Interation with Oracle AQs seem to be trivial as there is a native JCA based adapter for it
    * You may get performance hit because of the multiple connection points. You may be loosing performance but gaining in flexibility
    Overall Oracle BPEL seems to be the way to go if your business process involves multiple applications.
    HTH
    Rajesh

  • SOA Suite BPEL to OSB

    I am trying to create a simple proof of concept that calls OSB from a BPEL Process. I created a WSDL with an EchoService in OSB, I then created a partner link with the WSDL. When using the BPEL Debug Console I get an error:
    Faulted while invoking operation "echo" on provider "PartnerLink_1".
    - <messages>
    - <input>
    - <echoRequest>
    - <part xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" name="echoString">
    <echoString>
    hello
    </echoString>
    </part>
    </echoRequest>
    </input>
    - <fault>
    - <invalidVariables xmlns="http://schemas.oracle.com/bpel/extension">
    - <part name="code">
    <code>
    9710
    </code>
    </part>
    - <part name="summary">
    <summary>
    Invalid xml document.
    According to the xml schemas, the xml document is invalid. The reason is: Error::cvc-elt.1: Cannot find the declaration of element 'echoString'.
    Please make sure that the xml document is valid against your schemas.
    </summary>
    </part>
    </invalidVariables>
    </fault>
    </messages>
    =======wsdl=======
    <?xml version="1.0" encoding="UTF-8"?>
    <wsdl:definitions xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:http="http://schemas.xmlsoap.org/wsdl/http/" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/" xmlns:tns="http://new.webservice.namespace" targetNamespace="http://new.webservice.namespace">
         <wsdl:types>
              <xs:schema targetNamespace="http://new.webservice.namespace" elementFormDefault="qualified"/>
         </wsdl:types>
         <wsdl:message name="EchoRequest">
              <wsdl:part name="echoString" type="xs:string"/>
         </wsdl:message>
         <wsdl:message name="EchoResponse">
              <wsdl:part name="theEcho" type="xs:string"/>
         </wsdl:message>
         <wsdl:portType name="EchoServicePortType">
              <wsdl:operation name="echo">
                   <wsdl:input message="tns:EchoRequest" name="EchoRequest"/>
                   <wsdl:output message="tns:EchoResponse" name="EchoResponse"/>
              </wsdl:operation>
         </wsdl:portType>
         <wsdl:binding name="EchoServiceHttpBinding" type="tns:EchoServicePortType">
              <soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
              <wsdl:operation name="echo">
                   <soap:operation soapAction=""/>
                   <wsdl:input name="EchoRequest">
                        <soap:body use="literal"/>
                   </wsdl:input>
                   <wsdl:output name="EchoResponse">
                        <soap:body use="literal"/>
                   </wsdl:output>
              </wsdl:operation>
         </wsdl:binding>
         <wsdl:service name="EchoServiceImpl">
              <wsdl:port name="EchoServicePort" binding="tns:EchoServiceHttpBinding">
                   <soap:address location="http://mcarr-linux:7001//HelloWorld/WSDL/EchoProxyService"/>
              </wsdl:port>
         </wsdl:service>
    </wsdl:definitions>
    ======bpel======
    <?xml version = "1.0" encoding = "UTF-8" ?>
    <!--
    Oracle JDeveloper BPEL Designer
    Created: Fri Oct 31 14:24:55 PDT 2008
    Author: mcarr
    Purpose: Asynchronous BPEL Process
    -->
    <process name="ProcessFileToWS"
    targetNamespace="http://xmlns.oracle.com/ProcessFileToWS"
    xmlns="http://schemas.xmlsoap.org/ws/2003/03/business-process/"
    queryLanguage="http://www.w3.org/TR/1999/REC-xpath-19991116"
    expressionLanguage="http://www.w3.org/TR/1999/REC-xpath-19991116"
    abstractProcess="no" enableInstanceCompensation="no"
    xmlns:bpws="http://schemas.xmlsoap.org/ws/2003/03/business-process/"
    xmlns:xp20="http://www.oracle.com/XSL/Transform/java/oracle.tip.pc.services.functions.Xpath20"
    xmlns:ns4="http://www.oracle.com/XSL/Transform/java/oracle.tip.esb.server.headers.ESBHeaderFunctions"
    xmlns:ldap="http://schemas.oracle.com/xpath/extension/ldap"
    xmlns:xsd="http://www.w3.org/2001/XMLSchema"
    xmlns:ns5="http://www.oracle.com/XSL/Transform/java/oracle.tip.xref.xpath.XRefXPathFunctions"
    xmlns:client="http://xmlns.oracle.com/ProcessFileToWS"
    xmlns:ora="http://schemas.oracle.com/xpath/extension"
    xmlns:ns1="http://new.webservice.namespace"
    xmlns:ns3="http://xmlns.oracle.com/bpel/services/IdentityService/xpath"
    xmlns:ns2="http://xmlns.oracle.com/bpel/workflow/xpath"
    xmlns:bpelx="http://schemas.oracle.com/bpel/extension"
    xmlns:orcl="http://www.oracle.com/XSL/Transform/java/oracle.tip.pc.services.functions.ExtFunc">
    <!--
    PARTNERLINKS
    List of services participating in this BPEL process
    -->
    <!--
    VARIABLES
    List of messages and XML documents used within this BPEL process
    -->
    <partnerLinks>
    <partnerLink name="client" partnerLinkType="client:ProcessFileToWS"
    myRole="ProcessFileToWSProvider"
    partnerRole="ProcessFileToWSRequester"/>
    <partnerLink myRole="EchoServicePortType_Role" name="ProcessFileToWS"
    partnerRole="EchoServicePortType_Role"
    partnerLinkType="ns1:EchoServicePortType_PL"/>
    </partnerLinks>
    <variables>
    <!-- Reference to the message passed as input during initiation -->
    <!-- Reference to the message that will be sent back to the requester during callback -->
    <variable name="inputVariable"
    messageType="client:ProcessFileToWSRequestMessage"/>
    <variable name="outputVariable"
    messageType="client:ProcessFileToWSResponseMessage"/>
    <variable name="echoRequest" messageType="ns1:EchoRequest"/>
    <variable name="echoResponse" messageType="ns1:EchoResponse"/>
    </variables>
    <!--
    ORCHESTRATION LOGIC
    Set of activities coordinating the flow of messages across the
    services integrated within this business process
    -->
    <sequence name="main">
    <!-- Receive input from requestor. (Note: This maps to operation defined in ProcessFileToWS.wsdl) -->
    <receive name="receiveInput" partnerLink="client"
    portType="client:ProcessFileToWS" operation="initiate"
    variable="inputVariable" createInstance="yes"/>
    <!--
    Asynchronous callback to the requester. (Note: the callback location and correlation id is transparently handled using WS-addressing.)
    -->
    <assign name="Assign_1">
    <copy>
    <from variable="inputVariable" part="payload"
    query="/client:ProcessFileToWSProcessRequest/client:input"/>
    <to variable="echoRequest" part="echoString"/>
    </copy>
    </assign>
    <invoke name="Invoke_1" portType="ns1:EchoServicePortType"
    inputVariable="echoRequest" outputVariable="echoResponse"
    partnerLink="ProcessFileToWS" operation="echo"/>
    <assign name="Assign_2">
    <copy>
    <from variable="echoResponse" part="theEcho"/>
    <to variable="outputVariable" part="payload"/>
    </copy>
    </assign>
    <invoke name="callbackClient" partnerLink="client"
    portType="client:ProcessFileToWSCallback" operation="onResult"
    inputVariable="outputVariable"/>
    </sequence>
    </process>

    Try this wsdl for your OSB service. This assumes that you are running OSB on port 7021.
    It will create a service called Echo.
    cheers
    James
    <?xml version="1.0" encoding="UTF-8"?>
    <wsdl:definitions xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
    xmlns:tns="http://oracle.com/Echo/"
    xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
    xmlns:xsd="http://www.w3.org/2001/XMLSchema"
    name="Echo"
    targetNamespace="http://oracle.com/Echo/">
    <wsdl:types>
    <xsd:schema targetNamespace="http://oracle.com/Echo/">
    <xsd:element name="EchoRequest">
    <xsd:complexType>
    <xsd:sequence>
    <xsd:element name="echoString" type="xsd:string"/>
    </xsd:sequence>
    </xsd:complexType>
    </xsd:element>
    <xsd:element name="EchoResponse">
    <xsd:complexType>
    <xsd:sequence>
    <xsd:element name="theEcho" type="xsd:string"/>
    </xsd:sequence>
    </xsd:complexType>
    </xsd:element>
    </xsd:schema>
    </wsdl:types>
    <wsdl:message name="InitiateRequest">
    <wsdl:part element="tns:EchoRequest" name="parameters"/>
    </wsdl:message>
    <wsdl:message name="InitiateResponse">
    <wsdl:part element="tns:EchoResponse" name="parameters"/>
    </wsdl:message>
    <wsdl:portType name="Echo">
    <wsdl:operation name="Initiate">
    <wsdl:input message="tns:InitiateRequest"/>
    <wsdl:output message="tns:InitiateResponse"/>
    </wsdl:operation>
    </wsdl:portType>
    <wsdl:binding name="EchoSOAP" type="tns:Echo">
    <soap:binding style="document"
    transport="http://schemas.xmlsoap.org/soap/http"/>
    <wsdl:operation name="Initiate">
    <soap:operation soapAction="http://oracle.com/Echo/Initiate"/>
    <wsdl:input>
    <soap:body use="literal"/>
    </wsdl:input>
    <wsdl:output>
    <soap:body use="literal"/>
    </wsdl:output>
    </wsdl:operation>
    </wsdl:binding>
    <wsdl:service name="Echo">
    <wsdl:port binding="tns:EchoSOAP"
    name="EchoSOAP">
    <soap:address location="http://localhost:7021/Echo"/>
    </wsdl:port>
    </wsdl:service>
    </wsdl:definitions>

  • BPEL or OSB for reading data from db and then writing to another db

    Hi All,
    I have a requirement of reading the data from a table in one database and then writing into the table in another databas.I dont need any transformation on the data.
    I understand that i can do this by creating a BPEL process with DB adapters.
    Is there any better way of implementing this.I am new to OSB and If need to use OSB, then how can we do this in OSB and what are the advantages of using OSB over BPEL in implementing this.
    Thanks,
    ashok

    probably it would be much easier to develop everything in JDeveloper using DBAdapter.
    You can run it inside SOA Suite, but you don't even need BPEL, just use Mediator.
    Otherwise you can export all the JCA and WSDL and XSD paraphernalia from JDeveloper and import into OSB, it should run smoothly.
    How do you trigger the transfer? Polling the DB to look for new rows?

  • SOAP Tag causing issue integrating BPEL and OSB

    Hi,
    I have developed one project in which BPEL JMS adapter enqueues the message into JMS queue and OSB proxy service dequeues the message from that queue and process it further.
    Now, the problem is that BPEL JMS adapter doesn't add SOAP envelope/header/body tags to the message but OSB proxy service requires those tags to be there with the message. OSB proxy service gives the following error:
    "com.bea.wli.sb.context.BindingLayerException: The message must be an instance of: {http://schemas.xmlsoap.org/soap/envelope/}Envelope."
    Is there any way that OSB proxy service can process the message not having SOAP envelope tags attached to it.
    Thanks

    Hi mneelapu,
    Thanks for the solution. Could you let me know in which Variable JMS will capture the data because I need to assign the to the body variable before calling the Business servcie that is WSDL based.
    Thanks.

  • Howto access clustered direct binding Endpoint from OSB - SOA?

    Hello,
    I have one question in a clustered osb / soa envoirement. I a single instance to access a soa endpoint from the osb I use
    t3://serverip:8001/default/myProject/showUserDirectBinding
    what do I have to to if I have a a Cluster?
    I know i the WLS Console I have to add the Cluster Adress serverip1:8001 serverip2:8001
    But what to configure in the OSB Direct Binding?
    t3://serverip1:8001/default/myProject/showUserDirectBinding, t3://serverip2:8001/default/myProject/showUserDirectBinding ?
    Thanks you for you help
    Kind Regards
    Ben

    Hello Anuj,
    thank you for the quick response. I was just updating my post. My expectation is, that there has to be a cluster adress defined. Because when using lot of nodes, like 100+ or attaching new nodes to the cluster, i would be a bad way to always be forced to update the projects and deploy again.
    For setting the cluster adress i have found the documentation :
    http://download.oracle.com/docs/cd/E14571_01/core.1111/e12036/extend_soa.htm#insertedID18
    It is some how missleading. I can enter multiple cluster adresses here, why should I do this? How is this adress propagated to the nodes? And is this port custom? Or is this just a List of the Cluster Nodes, but where would be my cluster adress then?
    A Simpler Question, if I enter to my osb cluster the clusteraddress osbfoobar:1234 would the cluster(osb1:8001, osb2:8001) be accessable through osbfoobar:1234?
    Kind Regards
    Ben

  • OSB proxy service Calling OSB proxy service from BPEL

    Dear team,
    Wehave a requirement to call a Wsdl based OSB proxy service with sb protocol from SOA Composite from BPEL process.
    We created a wsdl based OSB proxyservice with sb protocol and deployed to OSB development server.
    We tried to export the wsdl and corresponding xsd files. sbconfig.jar got created.
    When we extracted the sbconfig file and placed the wsdl and xsd into the SOA composite.
    When we are trying to create a partnerlink, that OSB proxy service wsdl is not showing up.
    Please suggest.
    How to call OSB proxy service from BPEL..

    Hi,
    Here either you need to change the protocol from 'sb' to http or use the Direct Binding in soa-composite.
    please refer this links:
    Can a business service call a proxy service in OSB
    http://biemond.blogspot.in/2009/03/calling-osb-services-from-bpel.html
    BPEL to OSB using sb transport protocol
    Thanks,

  • How to integrate BPEL process with OSB?

    HI,
    I want to expose a web service from OSB and then after doing the initial validation of request,want the request xml to be forwarded to one of my BPEL process from where i would go for business processing with the request xml data.
    Could any one help me here, what are the steps to be followed to integrate BPEL and OSB such that i'll be able to get rquest xml from OSB and reply back the final response to OSB .OSB will respond back to external world.
    I have already exposed my webservice from OSB,but don't know how to forward this req xml to my BPEl process and finally fetch res from BPEL.

    Hi Arik,
    Thanks for Helping me out here. But my problem is when i m communicationg with the BPEl via default wsdl generated by my BPEl process, Through SAO-Direct from OSB.It's looking for binding tag in that WSDl which is not present when i created the BPEl process.
    for eg.
    In BPEl I have genarated a web service whose input and response is based on existing WSDL .This is the same WSDL which has been referred in OSB to intract with external world ( for upstream component who would be calling my web service).
    The default WSDL geneareted by this BPEl does have portType,message,partenerLincType. But it doesnot have binding tag.
    Now ,When i m trying to connect to this BPEl from OSB by creating new business service, while refering to this BPEl wsdl,It's looking for binding tag which is actually not present in default WSDL genarated by BPEL.
    So considering my explained scenario,will you plz help me, where m i going wrong and in this case what are the correct steps i should follow to fullfill me requirement.

  • OSB proxy service and BPEL depedency is not established in BTM

    Hi All,
    I am using BTM 12.1.0.3 and I have deployed a service where an OSB proxy service is taking employee information and callling a BPEL process which writes data in some database table. The OSB proxy service and BPEL got discovered in BTM but the dependecy between OSB Proxy service and BPEL process is not established in BTM. I have used soa-dorect protocol to call the BPEL from OSB. I have also tried with using http protocol in OSB for calling a BPEL but nothing worked and the depedency is not established in BTM.
    Now I want to create an end-toend transaction i.e. starting from OSB proxy to the database. For this I selected OSB proxy operation and BPEL operation but correlation is not established. How can I correlate these operation? And how can I create an end-to-end transaction for this type of service where OSB calls a BPEL?
    Please guide!!
    Thanks in advance!!

    you can manually correlate any number of services to create an end-2-end transaction. Please see http://docs.oracle.com/cd/E24628_01/doc.121/e37014/transactions004.htm#BABDBDFI on how to manually correlate services in BTM.

Maybe you are looking for

  • How do i setup an Exchange email account on a iphone 4 s

    How do I setup an Exchange account on a iphone 4 s

  • Armenian Mshtakan font not working in MS Word

    Hello, I am able to use the Armenian Mshtakan font on a Macbook pro using OS 10.7.5 only in Text Edit.  It will not work in MS Word. Is there any way to get Mshtakan font to work in MS Word for Mac?  Currently using MS Office 2011. Microsoft's websit

  • Trigger proxy when Process Order is released

    Dear ABAP Experts, I have a requirement where in I am supposed to send out a proxy with the details of the Process Order that is being released when the PO is released using COR2 or COHVPI transaction. The same can be achieved by coding in specific U

  • Having different color intensity in iPhoto from PSE4

    I organize and stop my photos in iPhoto 06. I do my editing in Photoshop Elements 4. I notice when I bring my photos from PSE4 back into iPhoto the intensity of the colors is a lot lighter. In other words, when I view a photo in PSE4 the color intens

  • Late 2010 17-inch MacBook Pro beach ball freeze

    Hi all, this is my second to last resort (last is sending in for repair xD). Well anyways, hope that you guys can help me solve this problem so I won't have to go there . Here's the story: I recently purchased a custom, late 2010 17-inch MacBook Pro