Web Service Reliability on ESB

Hi,
I am very new to ESB.
Requirement : is to call a reliable soap service from an ESB.
I need to enforce reliabilty on ESB to call a reliable web service.
Pls. let me know how can I acheive this.

Hi,
the new 2.1 version includes a test interface for business and proxy services.
-Kai

Similar Messages

  • Web Service reliable messaging in PI 7.1

    Hello Experts,
    I am working on a POC on Web Service Reliable Messaging.
    Anyone, Pls send me the detailed scenario on how to implement the same in PI 7.1.
    I have searched in SDN but i cud not find much info specific to this.
    Thanks in Advance.
    Regards,
    Swetha.

    Hi Swetha ,
    Please try:
    Configuring Web Services Reliable Messaging
    http://help.sap.com/saphelp_nwpi71/helpdata/en/46/741a3dfcfa0eede10000000a155369/content.htm
    Preview of Web Services Reliable Messaging in SAP NetWeaver Process Integration 7.1
    https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/304335f7-f33c-2a10-ae80-9c9ffdc86415
    Web Services-Based Connectivity
    Configuring Web Services Reliable Messaging
    https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/109aa318-5aa6-2a10-799d-a495383c1e01
    Regards
    joel
    Edited by: joel trinidade on Apr 9, 2009 11:05 AM

  • Web services reliable messaging in weblogic 9

    Hi Weblogic web services gurus,
    I have some questions regarding the reliable messaging support in wls9 of web services.
    1. Since the SAF used for persistent storage, does weblogic support the sequence recovery when system failures? Or sequence can't accorss system failures?
    2. For the response sequence created by the web services service provider, what is the RM policy used? From the the wsdl file, we can see the policy only attach to the input message part of operation section.
    Thank you very much!
    Wayne Chen

    Someone please reply. I'm clueless. Are they saying the webservices reliable messaging has already been implemented using ABAP LUW and is available in the workbench? If so how to use it ito create a reliable webservice? Why are they showing some PL/SQL like code then?  It is all unintelligible to me as I haven't used any of these.
    Edited by: convicted on May 11, 2011 10:59 AM

  • BPEL using Web Service Reliability..

    Hi,
    i found in Oracle Application Server Advanced Web Services Deployment Guide (B28975-01) / chapter 5 that there is a way to build webservices with guaranteed delivery and duplication elimination.
    Now my question:
    How do i have to configure the BPEL to be aware of this reliability feature?

    Hello,
    BPEL does not support entirely WS-Reliability today, but you should be able to activate it on the inbound service (the one you use to invoke the BPEL itself). You can do it after deployment from the Application Server Control administration pages.
    Can you describe your exact scenario? Where do you want to put reliability?
    Regards
    Tugdual Grall

  • Web service reliable messaging on NW70 java

    Hi all,
    I need to ensure reliable messaging both in consuming and providing web services in a NW70-based java application.
    I know that WSRM is enabled on NW71.
    Can that be done on NW70 java too?
    Thanks, regards
    Vincenzo

    not doable

  • SOAP Reliable Messaging (8.1) vs. Web Service Reliable Messaging (9.0)

    I am looking for the differences in implementation and user experience for two Reliable Messaging solutions ( besides that WL 9.0 implemented WS-RM Spec. ). In particular, when a Reliable Messaging transaction is committed and successfully complete, which consumer element/component on the receiver side gets the message and how ( I mean a run-time component which is not implemented by WL on the receiver side) ? Does the message stay in receiver side persistent storage until it is taken by the consumer element/component or it sits in memory only ?
    Docs in 8.1 version detailed how the SOAP RM worked while in 9.0 version such description is absent.
    Please, send your response to [email protected]
    Thank you in advance,
    - Michael

    Hi,
    i think its not possible to get the response of the return type as void. you just think in normal core java also, its not possible that. i think you must change in the web service. and one more thing are you developing the web service in java or .NET? if it in java its easy to change the return type. i am also new to java web service. i am giving what i know.
    Thanks

  • Failure upon calling web service on the ESB deployed from jDeveloper

    Hello!
    I've created a database adapter and a routing service that calls the database adapter. When registering the services on the ESB, I get error when I try to call it, as the Wsdl references a wsdl file on http://localhost:8888...... As I see it, it should refer to in on the same server as the esb (soa suite) runs? I think this might be a deployment issue in jDeveloper, maybe ant? Any clue on this?
    brgds, Paul Jørstad

    Thank you very much for you reply!
    But I do not get any further.. In the ESB control, the Soap Endpoint URI still says:
    SOAP Endpoint URI
    http://localhost:8888/event/xal/rs_product_p_get_complete_bom_flat
    And in my wsdl file:
    <soap:address location="http://oslsoad1/event/xal/rs_product_p_get_complete_bom_flat"/>
    I've tried to de-register, and register the service.

  • Web Services Reliable Messaging

    Does Oracle BPEL PM has WSRM implemented
    1.As Server to expose WSRM based service ?
    2.To consume other WSRM services ?
    If so, what other app servers the interoperability is tested ?
    regards,
    Arun

    BPEL PM does not support WS-RM .. But you can use Oracle's Webservice Manager, that should contain this feature as part of its SLA management ..
    hth clemens

  • Web Services reliable messaging is not supported in SAP AS 7.0?

    In 7.1 documentation, I find that one enables a webservice for reliable messaging by writing @RelMessagingNW05DTOperation annotation.
    However I'm shocked to find that in 7.0 documentation, it only talks about some PL/SQL like code (LUW) that one has to implement to have reliable messaging (http://help.sap.com/saphelp_nw70ehp2/helpdata/en/46/9743916d1115ece10000000a114a6b/frameset.htm). As I'm not familiar with LUW, can you confirm that the developer himself has to handle creating sequences, reordering them and guaranteeing exactly once delivery? And the LUW code shown in the link, does it do all this?
    Please advice.

    Someone please reply. I'm clueless. Are they saying the webservices reliable messaging has already been implemented using ABAP LUW and is available in the workbench? If so how to use it ito create a reliable webservice? Why are they showing some PL/SQL like code then?  It is all unintelligible to me as I haven't used any of these.
    Edited by: convicted on May 11, 2011 10:59 AM

  • Web Service Reliable Messaging: Namespace confusion / bug

    Hello,
    according to the 9.2 doc and IMHO the spec the correct namespace for RM1.0 assertions is:
    xmlns:wsrm="http://schemas.xmlsoap.org/ws/2005/02/rm/policy
    however, the packaged example uses
    xmlns:wsrm="http://schemas.xmlsoap.org/ws/2005/02/rm
    even worse, this is the only way to get it to work!
    does that mean I have to use a wrong namespace to get a working WS-RM example for the latest WLS9.2MP3?
    thanks for your input.
    Barossa

    ok, it does work with the rm namespace. I have no idea why, as this should be a completely different schema.
    also it works with the correct namespace rm/policy (which is more restrictive, first I had an ExponentialBackoff element
    in the wrong order, for the rm namespace it was ok, but not for the rm/policy.)
    so the example is plain wrong. the namespace and even the sequence of the elements. still it is working. how does that come?
    Edited by: Barossa on Jan 22, 2009 6:35 PM

  • Enable WSRM (Web Service Reliable Messaging) in sap system

    Hi All,
    Can any one provide document to enable wsrm in sap pi system.
    your help is much appreciated
    Thanks,
    Narendar.

    Hi,
    Please check below link it will help you.
    http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/107256c4-d4c4-2d10-fca1-d1676081892b?QuickLink=index&…
    Best Regards,
    Atul

  • ESB and Stateful web services

    Folks,
    I’ve got two web services that are called in succession. The first web service performs a search and caches the results on the server, returning only some basic information about how many results were found (in the payload) and a session id (as an attribute in a HTTP header). The second service is called afterwards, passing some page request information (in payload) and the session id (in the HTTP header). The session id is used to find the appropriate search results and return them lazily (based the given page request information).
    The web service requests are done through ESB and OWSM. My problem, however, is that according to the ESB developer’s guide (http://download-west.oracle.com/docs/cd/B31017_01/integrate.1013/b28211.pdf , page 5-29, ‘Limitations of ESB Header Support’) ESB is not capable of setting header attributes (at least not SOAP header attributes).
    Is it possible to use stateful web services with the ESB? If so, how is the SessionID handled on the ESB and how is it correlated with the clients of the ESB who are getting the results back from this stateful web service?
    Thanks in advance,
    Joseph

    Dave,
    We have invoked the two services mentioned above in four different manners using Java code.
    1. We are invoking the services through ESB with no success. The HTTP header (set-cookie) never makes it back.
    2. We are invoking the services through Web Services Manager (the services are registered directly with OWSM) with no success. The HTTP header (set-cookie) never makes it back.
    3. We are invoking the services through Web Services Manager (with ESB providing a wrapper for the services) with no success. The HTTP header never (set-cookie) makes it back.
    4. Invoking the services directly (no OWSM, no ESB). This method is successful. HTTP headers are being exchanged without incident.
    We are using Ethereal to check out the traffic going back and forth so we can see the SOAP headers getting propagated back and forth as you had mentioned. The problem is that the HTTP headers (as mentioned in my first posting) containing the session information are getting dropped when using ESB or Web Services Manager.
    Any suggestions?
    Thanks,
    Joseph

  • Error while testing a web service using JMSAdapter in ESB

    Hi,
    I have configured a JMS adapter to produce a message on a Topic.
    When ever I test the web service to invoke this service I get the following 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:Server</faultcode><faultstring>oracle.tip.esb.server.common.exceptions.BusinessEventRetriableException: An unhandled exception has been thrown in the ESB system. The exception reported is: "oracle.tip.esb.server.common.exceptions.BusinessEventRejectionException: An unhandled exception has been thrown in the ESB system. The exception reported is: "org.collaxa.thirdparty.apache.wsif.WSIFException: esb:///ESB_Projects/LearningESB_AQJMS2DB/ProduceTestMsg.wsdl [ Produce_Message_ptt::Produce_Message(InputParameters) ] - WSIF JCA Execute of operation 'Produce_Message' failed due to: Adapter Framework unable to create outbound JCA connection.
    esb:///ESB_Projects/LearningESB_AQJMS2DB/ProduceTestMsg.wsdl [ Produce_Message_ptt::Produce_Message(InputParameters) ] - : The Adapter Framework was unable to establish an outbound JCA connection due to the following issue: ORABPEL-12529
    ManagedConnectionFactory problem.
    Could not instantiate ManagedConnectionFactory oracle.tip.adapter.jms.JmsManagedConnectionFactory due to:
         Missing class: oracle.tip.adapter.jms.JmsManagedConnectionFactory
         Dependent class: oracle.tip.adapter.fw.wsdl.WSDLUtils
         Loader: oracle.bpel.common:10.1.3
         Code-Source: /oraclesoa/oraclesoa/product/10.1.3.1/OracleAS_1/bpel/lib/orabpel.jar
         Configuration: &lt;code-source&gt; in /oraclesoa/oraclesoa/product/10.1.3.1/OracleAS_1/j2ee/home/config/server.xml
    This load was initiated at esb-rt.web.provider-war:0.0.0 using the Class.forName() method.
    The missing class is not available from any code-source or loader in the system.
    Please make sure the corresponding JCA Resource Adapter has been deployed.
    ; nested exception is:
         ORABPEL-12511
    Adapter Framework unable to create outbound JCA connection.
    esb:///ESB_Projects/LearningESB_AQJMS2DB/ProduceTestMsg.wsdl [ Produce_Message_ptt::Produce_Message(InputParameters) ] - : The Adapter Framework was unable to establish an outbound JCA connection due to the following issue: ORABPEL-12529
    ManagedConnectionFactory problem.
    Could not instantiate ManagedConnectionFactory oracle.tip.adapter.jms.JmsManagedConnectionFactory due to:
         Missing class: oracle.tip.adapter.jms.JmsManagedConnectionFactory
         Dependent class: oracle.tip.adapter.fw.wsdl.WSDLUtils
         Loader: oracle.bpel.common:10.1.3
         Code-Source: /oraclesoa/oraclesoa/product/10.1.3.1/OracleAS_1/bpel/lib/orabpel.jar
         Configuration: &lt;code-source&gt; in /oraclesoa/oraclesoa/product/10.1.3.1/OracleAS_1/j2ee/home/config/server.xml
    This load was initiated at esb-rt.web.provider-war:0.0.0 using the Class.forName() method.
    The missing class is not available from any code-source or loader in the system.
    Please make sure the corresponding JCA Resource Adapter has been deployed.
    Please examine the log file for any reasons. Enable DEBUG logging in the BPEL Console.
         at oracle.tip.adapter.fw.wsif.jca.WSIFOperation_JCA.executeRequestResponseOperation(WSIFOperation_JCA.java:623)
         at oracle.tip.adapter.fw.wsif.jca.WSIFOperation_JCA.executeInputOnlyOperation(WSIFOperation_JCA.java:726)
         at oracle.tip.esb.server.common.wsif.WSIFInvoker.executeOperation(Unknown Source)
         at oracle.tip.esb.server.common.wsif.WSIFInvoker.nextService(Unknown Source)
         at oracle.tip.esb.server.common.wsif.WSIFInvoker.nextService(Unknown Source)
         at oracle.tip.esb.server.service.impl.outadapter.OutboundAdapterService.nextService(Unknown Source)
         at oracle.tip.esb.server.service.impl.outadapter.OutboundAdapterService.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.server.service.impl.soap.EventOracleSoapProvider.raiseEvent(Unknown Source)
         at oracle.tip.esb.server.service.impl.soap.EventOracleSoapProvider.processMessage(Unknown Source)
         at oracle.j2ee.ws.server.provider.ProviderProcessor.doEndpointProcessing(ProviderProcessor.java:869)
         at oracle.j2ee.ws.server.WebServiceProcessor.invokeEndpointImplementation(WebServiceProcessor.java:349)
         at oracle.j2ee.ws.server.provider.ProviderProcessor.doRequestProcessing(ProviderProcessor.java:460)
         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:711)
         at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:368)
         at com.evermind.server.http.HttpRequestHandler.doProcessRequest(HttpRequestHandler.java:866)
         at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:448)
         at com.evermind.server.http.HttpRequestHandler.serveOneRequest(HttpRequestHandler.java:216)
         at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:117)
         at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:110)
         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: ORABPEL-12511
    Adapter Framework unable to create outbound JCA connection.
    esb:///ESB_Projects/LearningESB_AQJMS2DB/ProduceTestMsg.wsdl [ Produce_Message_ptt::Produce_Message(InputParameters) ] - : The Adapter Framework was unable to establish an outbound JCA connection due to the following issue: ORABPEL-12529
    ManagedConnectionFactory problem.
    Could not instantiate ManagedConnectionFactory oracle.tip.adapter.jms.JmsManagedConnectionFactory due to:
         Missing class: oracle.tip.adapter.jms.JmsManagedConnectionFactory
         Dependent class: oracle.tip.adapter.fw.wsdl.WSDLUtils
         Loader: oracle.bpel.common:10.1.3
         Code-Source: /oraclesoa/oraclesoa/product/10.1.3.1/OracleAS_1/bpel/lib/orabpel.jar
         Configuration: &lt;code-source&gt; in /oraclesoa/oraclesoa/product/10.1.3.1/OracleAS_1/j2ee/home/config/server.xml
    This load was initiated at esb-rt.web.provider-war:0.0.0 using the Class.forName() method.
    The missing class is not available from any code-source or loader in the system.
    Please make sure the corresponding JCA Resource Adapter has been deployed.
    Please examine the log file for any reasons. Enable DEBUG logging in the BPEL Console.
         at oracle.tip.adapter.fw.wsif.jca.WSIFPort_JCA$JCAConnectionPool.createJCAConnectionFactory(WSIFPort_JCA.java:1585)
         at oracle.tip.adapter.fw.wsif.jca.WSIFPort_JCA$JCAConnectionPool.newPoolObject(WSIFPort_JCA.java:1439)
         at oracle.tip.adapter.fw.common.ObjectPool.checkOut(ObjectPool.java:125)
         at oracle.tip.adapter.fw.wsif.jca.WSIFPort_JCA$JCAConnectionPool.checkOut(WSIFPort_JCA.java:1656)
         at oracle.tip.adapter.fw.wsif.jca.WSIFPort_JCA.obtainJCAConnection(WSIFPort_JCA.java:984)
         at oracle.tip.adapter.fw.wsif.jca.WSIFOperation_JCA.executeRequestResponseOperation(WSIFOperation_JCA.java:327)
         ... 32 more
    Caused by: ORABPEL-12529
    ManagedConnectionFactory problem.
    Could not instantiate ManagedConnectionFactory oracle.tip.adapter.jms.JmsManagedConnectionFactory due to:
         Missing class: oracle.tip.adapter.jms.JmsManagedConnectionFactory
         Dependent class: oracle.tip.adapter.fw.wsdl.WSDLUtils
         Loader: oracle.bpel.common:10.1.3
         Code-Source: /oraclesoa/oraclesoa/product/10.1.3.1/OracleAS_1/bpel/lib/orabpel.jar
         Configuration: &lt;code-source&gt; in /oraclesoa/oraclesoa/product/10.1.3.1/OracleAS_1/j2ee/home/config/server.xml
    This load was initiated at esb-rt.web.provider-war:0.0.0 using the Class.forName() method.
    The missing class is not available from any code-source or loader in the system.
    Please make sure the corresponding JCA Resource Adapter has been deployed.
         at oracle.tip.adapter.fw.wsdl.WSDLUtils.setupManagedConnectionFactory(WSDLUtils.java:461)
         at oracle.tip.adapter.fw.wsif.jca.WSIFPort_JCA$JCAConnectionPool.createJCAConnectionFactory(WSIFPort_JCA.java:1517)
         ... 37 more
    Caused by: oracle.classloader.util.AnnotatedClassNotFoundException:
         Missing class: oracle.tip.adapter.jms.JmsManagedConnectionFactory
         Dependent class: oracle.tip.adapter.fw.wsdl.WSDLUtils
         Loader: oracle.bpel.common:10.1.3
         Code-Source: /oraclesoa/oraclesoa/product/10.1.3.1/OracleAS_1/bpel/lib/orabpel.jar
         Configuration: &lt;code-source&gt; in /oraclesoa/oraclesoa/product/10.1.3.1/OracleAS_1/j2ee/home/config/server.xml
    This load was initiated at esb-rt.web.provider-war:0.0.0 using the Class.forName() method.
    The missing class is not available from any code-source or loader in the system.
         at oracle.classloader.PolicyClassLoader.handleClassNotFound(PolicyClassLoader.java:2078)
         at oracle.classloader.PolicyClassLoader.internalLoadClass(PolicyClassLoader.java:1679)
         at oracle.classloader.PolicyClassLoader.loadClass(PolicyClassLoader.java:1635)
         at oracle.classloader.PolicyClassLoader.loadClass(PolicyClassLoader.java:1620)
         at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319)
         at java.lang.Class.forName0(Native Method)
         at java.lang.Class.forName(Class.java:242)
         at oracle.tip.adapter.fw.wsdl.WSDLUtils.setupManagedConnectionFactory(WSDLUtils.java:454)
         ... 38 more
         at oracle.tip.esb.server.common.wsif.WSIFInvoker.executeOperation(Unknown Source)
         at oracle.tip.esb.server.common.wsif.WSIFInvoker.nextService(Unknown Source)
         at oracle.tip.esb.server.common.wsif.WSIFInvoker.nextService(Unknown Source)
         at oracle.tip.esb.server.service.impl.outadapter.OutboundAdapterService.nextService(Unknown Source)
         at oracle.tip.esb.server.service.impl.outadapter.OutboundAdapterService.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.server.service.impl.soap.EventOracleSoapProvider.raiseEvent(Unknown Source)
         at oracle.tip.esb.server.service.impl.soap.EventOracleSoapProvider.processMessage(Unknown Source)
         at oracle.j2ee.ws.server.provider.ProviderProcessor.doEndpointProcessing(ProviderProcessor.java:869)
         at oracle.j2ee.ws.server.WebServiceProcessor.invokeEndpointImplementation(WebServiceProcessor.java:349)
         at oracle.j2ee.ws.server.provider.ProviderProcessor.doRequestProcessing(ProviderProcessor.java:460)
         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:711)
         at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:368)
         at com.evermind.server.http.HttpRequestHandler.doProcessRequest(HttpRequestHandler.java:866)
         at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:448)
         at com.evermind.server.http.HttpRequestHandler.serveOneRequest(HttpRequestHandler.java:216)
         at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:117)
         at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:110)
         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: org.collaxa.thirdparty.apache.wsif.WSIFException: esb:///ESB_Projects/LearningESB_AQJMS2DB/ProduceTestMsg.wsdl [ Produce_Message_ptt::Produce_Message(InputParameters) ] - WSIF JCA Execute of operation 'Produce_Message' failed due to: Adapter Framework unable to create outbound JCA connection.
    esb:///ESB_Projects/LearningESB_AQJMS2DB/ProduceTestMsg.wsdl [ Produce_Message_ptt::Produce_Message(InputParameters) ] - : The Adapter Framework was unable to establish an outbound JCA connection due to the following issue: ORABPEL-12529
    ManagedConnectionFactory problem.
    Could not instantiate ManagedConnectionFactory oracle.tip.adapter.jms.JmsManagedConnectionFactory due to:
         Missing class: oracle.tip.adapter.jms.JmsManagedConnectionFactory
         Dependent class: oracle.tip.adapter.fw.wsdl.WSDLUtils
         Loader: oracle.bpel.common:10.1.3
         Code-Source: /oraclesoa/oraclesoa/product/10.1.3.1/OracleAS_1/bpel/lib/orabpel.jar
         Configuration: &lt;code-source&gt; in /oraclesoa/oraclesoa/product/10.1.3.1/OracleAS_1/j2ee/home/config/server.xml
    This load was initiated at esb-rt.web.provider-war:0.0.0 using the Class.forName() method.
    The missing class is not available from any code-source or loader in the system.
    Please make sure the corresponding JCA Resource Adapter has been deployed.
    ; nested exception is:
         ORABPEL-12511
    Adapter Framework unable to create outbound JCA connection.
    esb:///ESB_Projects/LearningESB_AQJMS2DB/ProduceTestMsg.wsdl [ Produce_Message_ptt::Produce_Message(InputParameters) ] - : The Adapter Framework was unable to establish an outbound JCA connection due to the following issue: ORABPEL-12529
    ManagedConnectionFactory problem.
    Could not instantiate ManagedConnectionFactory oracle.tip.adapter.jms.JmsManagedConnectionFactory due to:
         Missing class: oracle.tip.adapter.jms.JmsManagedConnectionFactory
         Dependent class: oracle.tip.adapter.fw.wsdl.WSDLUtils
         Loader: oracle.bpel.common:10.1.3
         Code-Source: /oraclesoa/oraclesoa/product/10.1.3.1/OracleAS_1/bpel/lib/orabpel.jar
         Configuration: &lt;code-source&gt; in /oraclesoa/oraclesoa/product/10.1.3.1/OracleAS_1/j2ee/home/config/server.xml
    This load was initiated at esb-rt.web.provider-war:0.0.0 using the Class.forName() method.
    The missing class is not available from any code-source or loader in the system.
    Please make sure the corresponding JCA Resource Adapter has been deployed.
    Please examine the log file for any reasons. Enable DEBUG logging in the BPEL Console.
         at oracle.tip.adapter.fw.wsif.jca.WSIFOperation_JCA.executeRequestResponseOperation(WSIFOperation_JCA.java:623)
         at oracle.tip.adapter.fw.wsif.jca.WSIFOperation_JCA.executeInputOnlyOperation(WSIFOperation_JCA.java:726)
         ... 31 more
    Caused by: ORABPEL-12511
    Adapter Framework unable to create outbound JCA connection.
    esb:///ESB_Projects/LearningESB_AQJMS2DB/ProduceTestMsg.wsdl [ Produce_Message_ptt::Produce_Message(InputParameters) ] - : The Adapter Framework was unable to establish an outbound JCA connection due to the following issue: ORABPEL-12529
    ManagedConnectionFactory problem.
    Could not instantiate ManagedConnectionFactory oracle.tip.adapter.jms.JmsManagedConnectionFactory due to:
         Missing class: oracle.tip.adapter.jms.JmsManagedConnectionFactory
         Dependent class: oracle.tip.adapter.fw.wsdl.WSDLUtils
         Loader: oracle.bpel.common:10.1.3
         Code-Source: /oraclesoa/oraclesoa/product/10.1.3.1/OracleAS_1/bpel/lib/orabpel.jar
         Configuration: &lt;code-source&gt; in /oraclesoa/oraclesoa/product/10.1.3.1/OracleAS_1/j2ee/home/config/server.xml
    This load was initiated at esb-rt.web.provider-war:0.0.0 using the Class.forName() method.
    The missing class is not available from any code-source or loader in the system.
    Please make sure the corresponding JCA Resource Adapter has been deployed.
    Please examine the log file for any reasons. Enable DEBUG logging in the BPEL Console.
         at oracle.tip.adapter.fw.wsif.jca.WSIFPort_JCA$JCAConnectionPool.createJCAConnectionFactory(WSIFPort_JCA.java:1585)
         at oracle.tip.adapter.fw.wsif.jca.WSIFPort_JCA$JCAConnectionPool.newPoolObject(WSIFPort_JCA.java:1439)
         at oracle.tip.adapter.fw.common.ObjectPool.checkOut(ObjectPool.java:125)
         at oracle.tip.adapter.fw.wsif.jca.WSIFPort_JCA$JCAConnectionPool.checkOut(WSIFPort_JCA.java:1656)
         at oracle.tip.adapter.fw.wsif.jca.WSIFPort_JCA.obtainJCAConnection(WSIFPort_JCA.java:984)
         at oracle.tip.adapter.fw.wsif.jca.WSIFOperation_JCA.executeRequestResponseOperation(WSIFOperation_JCA.java:327)
         ... 32 more
    Caused by: ORABPEL-12529
    ManagedConnectionFactory problem.
    Could not instantiate ManagedConnectionFactory oracle.tip.adapter.jms.JmsManagedConnectionFactory due to:
         Missing class: oracle.tip.adapter.jms.JmsManagedConnectionFactory
         Dependent class: oracle.tip.adapter.fw.wsdl.WSDLUtils
         Loader: oracle.bpel.common:10.1.3
         Code-Source: /oraclesoa/oraclesoa/product/10.1.3.1/OracleAS_1/bpel/lib/orabpel.jar
         Configuration: &lt;code-source&gt; in /oraclesoa/oraclesoa/product/10.1.3.1/OracleAS_1/j2ee/home/config/server.xml
    This load was initiated at esb-rt.web.provider-war:0.0.0 using the Class.forName() method.
    The missing class is not available from any code-source or loader in the system.
    Please make sure the corresponding JCA Resource Adapter has been deployed.
         at oracle.tip.adapter.fw.wsdl.WSDLUtils.setupManagedConnectionFactory(WSDLUtils.java:461)
         at oracle.tip.adapter.fw.wsif.jca.WSIFPort_JCA$JCAConnectionPool.createJCAConnectionFactory(WSIFPort_JCA.java:1517)
         ... 37 more
    Caused by: oracle.classloader.util.AnnotatedClassNotFoundException:
         Missing class: oracle.tip.adapter.jms.JmsManagedConnectionFactory
         Dependent class: oracle.tip.adapter.fw.wsdl.WSDLUtils
         Loader: oracle.bpel.common:10.1.3
         Code-Source: /oraclesoa/oraclesoa/product/10.1.3.1/OracleAS_1/bpel/lib/orabpel.jar
         Configuration: &lt;code-source&gt; in /oraclesoa/oraclesoa/product/10.1.3.1/OracleAS_1/j2ee/home/config/server.xml
    This load was initiated at esb-rt.web.provider-war:0.0.0 using the Class.forName() method.
    The missing class is not available from any code-source or loader in the system.
         at oracle.classloader.PolicyClassLoader.handleClassNotFound(PolicyClassLoader.java:2078)
         at oracle.classloader.PolicyClassLoader.internalLoadClass(PolicyClassLoader.java:1679)
         at oracle.classloader.PolicyClassLoader.loadClass(PolicyClassLoader.java:1635)
         at oracle.classloader.PolicyClassLoader.loadClass(PolicyClassLoader.java:1620)
         at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319)
         at java.lang.Class.forName0(Native Method)
         at java.lang.Class.forName(Class.java:242)
         at oracle.tip.adapter.fw.wsdl.WSDLUtils.setupManagedConnectionFactory(WSDLUtils.java:454)
         ... 38 more
    </faultstring><faultactor></faultactor></env:Fault></env:Body></env:Envelope>
    I have done the following :_
    In the oc4j-ra.xml file located at /Oracle_Home/j2ee/home/application-deployments/default/JmsAdapter
    <connector-factory location="eis/Jms/OEMS" connector-name="JmsAdapter">
    <config-property name="connectionFactoryLocation" value="java:comp/resource/OEMS/TopicConnectionFactories/yTCF"/>
    <config-property name="factoryProperties" value=""/>
    <config-property name="acknowledgeMode" value="AUTO_ACKNOWLEDGE"/>
    <config-property name="isTopic" value="true"/>
    <config-property name="isTransacted" value="false"/>
    <config-property name="username" value="jmsuser"/>
    <config-property name="password" value="jmsuser"/>
    <connection-pooling use="none"></connection-pooling>
    <security-configuse="none"></security-config>
    </connector-factory>
    the application.xml file has the following :
    <resource-provider class="oracle.jms.OjmsContext" name="OEMS">
    <description>Resource provider for the OEMS database</description>
    <property name="url" value="jdbc:oracle:thin:jmsuser/jmsuser@localhost:1521:XE" />
    </resource-provider>
    Localhost , XE : this is replaced with the Database host name and service name on which the Topic is hosted .
    The application-client.xml file located at /Oracle_Home/bpel/system/classes/META-INF has the following :
    <application-client/>
    Plz let me know how can i go about to resolve this issue .
    Thanks
    Shilpa

    your problem:
    Missing class: oracle.tip.adapter.jms.JmsManagedConnectionFactory
    Dependent class: oracle.tip.adapter.fw.wsdl.WSDLUtils
    Loader: oracle.bpel.common:10.1.3
    Code-Source: /oraclesoa/oraclesoa/product/10.1.3.1/OracleAS_1/bpel/lib/orabpel.jar
    Configuration: <code-source> in /oraclesoa/oraclesoa/product/10.1.3.1/OracleAS_1/j2ee/home/config/server.xml
    It happens when server is custom installed, try to reinstall it as full version and problem should disappear otherwise your need another full installation to retrieve and replace orabpel.jar file from (or maybe more)

  • ESB Invokes Web Service More than once

    Hi,
    I have an ESB that invokes a Web Service Asynchronously (Using SOAP). In certain scenarios Web Service takes as much as 5 minutes to complete its operations. In such cases i am able to see ESB generating multiple requests to the Web Service. Multiple Requests are not generated in case Web Service completes its operations within a shorter duration (duration is based on business scenarios). I tried invoking the web service directly and i found that web service is invoked only once even when it takes 5 minutes.
    Please let me know if any of you have faced similair problems and also any possible ways of resolving this issue.
    Thanks,
    Rajesh

    We found that the default retry property of esb was the root cause of the issue. But still why should the esb retry as the call to webservice is an async one. The ESB should have completed the process.
    Why 5 minutes - Webservice performs a lot of validations and also the environment is a development one and not optimized.
    Regards,
    M.Rajesh

  • Error while testing Reliable messaging web service in OSB

    Hi
    following is the way i m doing ...
    1. i create a simple web service HelloWorld
    2.i publish and tested this webservice...it worked
    3. than i created business service in OSB and used the WSDL of the above webservice
    4. i created proxy service linked to above business service ,i used protocol as "WS" and attach defaultreliabilty policy to this proxy service
    5.now when i exported the wsdl of above proxy and tried to using SOAPUI and passing WS-reliable Msg header it is giving following error:
    <env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/">
    <env:Header/>
    <env:Body>
    <env:Fault>
    <faultcode>env:Server</faultcode>
    <faultstring>String index out of range: -6
    </faultstring>
    <detail>
    <bea_fault:stacktrace xmlns:bea_fault="http://www.bea.com/servers/wls70/webservice/fault/1.0.0">java.lang.StringIndexOutOfBoundsException: String index out of range: -6
         at java.lang.String.substring(String.java:1938)
         at weblogic.wsee.cluster.ForwardingHandler.handleRequest(ForwardingHandler.java:146)
         at weblogic.wsee.handler.HandlerIterator.handleRequest(HandlerIterator.java:141)
         at weblogic.wsee.ws.dispatch.server.ServerDispatcher.dispatch(ServerDispatcher.java:114)
         at weblogic.wsee.ws.WsSkel.invoke(WsSkel.java:80)
         at weblogic.wsee.server.servlet.SoapProcessor.handlePost(SoapProcessor.java:66)
         at weblogic.wsee.server.servlet.SoapProcessor.process(SoapProcessor.java:44)
         at weblogic.wsee.server.servlet.BaseWSServlet$AuthorizedInvoke.run(BaseWSServlet.java:285)
         at weblogic.wsee.server.servlet.BaseWSServlet.service(BaseWSServlet.java:169)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
         at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
         at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
         at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:292)
         at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:175)
         at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3498)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
         at weblogic.security.service.SecurityManager.runAs(Unknown Source)
         at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2180)
         at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2086)
         at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1406)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    </bea_fault:stacktrace>
    </detail>
    </env:Fault>
    </env:Body>
    </env:Envelope>
    The request for above response is:
    <env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ns1="http://docs.oasis-open.org/ws-rx/wsrm/200702" xmlns:ns2="http://com/">
    <env:Header>
    <ns1:Sequence>
    <ns1:Identifier>uuid:821e592a-2eef-4332-aed9-767177d62559</ns1:Identifier>
    <ns1:MessageNumber>5454</ns1:MessageNumber>
    </ns1:Sequence>
    </env:Header>
    <env:Body>
    <ns2:getWelcome>
    <arg0>5</arg0>
    </ns2:getWelcome>
    </env:Body>
    </env:Envelope>
    Do any one what is the problem???????????

    can you try to add 'transport headers' to the route of the business service, and select the checkbox ''Pass all Headers'
    and test again

Maybe you are looking for