OSB: Issue while testing OSB proxy service using SOAPUI

Hi,
I am trying to test an OSB proxy service using SOAPUI.
The below are the steps i have followed in SOAPUI:
1. File->New SOAPUI project
2. Opens the dialog to create REST service
3. Given service endpoint as: http://<osb servername>:<port>
4. Opens dialog to create a REST resource
5. Resource Path/EndPoint is the OSB proxy service end point.
6. HTTP method = POST
The proxy service accepts 'text' input so i have given Media Type as 'text/plain'
But, when i give the request message and run the request. The request is not running. I am not seeing the processing symbol at the bottom right of the SOAP UI request. Whereas i am able to run other services.
Kindly help me resolve this issue.
Thanks,
Kalpana.

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)

Similar Messages

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

  • Problem in testing a Web service using SOAPUI

    Hi Experts,
    I have developed a web service in our ECC 6.0 and download the WSDL file generated from SE80. When i downloaded the file, it saved as only XML file.  As I dont have JAVA stack in the ECC 6.0, i was testing using SOAPUI. But when i try to upload the file, it always says "Found nothing to import <URL>".
    Can anyone help me why it is giving this error? I still doubt there is some problem with the WSDL file which is generated for the service.
    Please guide me how to check the WSDL file generated is correct or not?
    Cheers,
    Madhu

    Thanks for the blog Salil.
    What ever it is mentioned is already done in SOAMANAGER. Endpoints are available for the service.
    Below is the Overview of the service:
    Object Status:               Services: 1 / Endpoints: 1 
    Porttype Namespace:   urn:sap-com:document:sap:soap:functions:mc-style
    Porttype Name:             YMTEST_WS
    Internal Name:               YMTEST_WS
    SOAP Applikation:         URN:SAP-COM:SOAP:RUNTIME:APPLICATION:RFC:710
    Package Name:             $TMP
    Ok, i have developed 2 web services. One web service in ECC 6.0, where Java stack not available so i provided CRM system Java stack address in the global setting and executed my ECC 6.0 web service which says "No endpoints are found for the Web service"
    Following is the URL:  http://tuasd06db.tuasw2k.tuaspower.com.sg:8000/sap/bc/srt/wsdl/sdef_YMTEST_WS/wsdl11/ws_policy/document?sap-client=220
    The one web service which created in CRM 2007, i can test in the navigator, no problem with that. 
    Following is the URL: 
    http://tuasd06db.tuasw2k.tuaspower.com.sg:8002/sap/bc/srt/wsdl/bndg_DE7DA5BA0B3A93F1AF60001A64258BFC/wsdl11/allinone/standard/document?sap-client=220
    You can find the URL difference btw the URL's. Do i need to publish the service in the service registry? I thought for testing it is not required.
    Now all i have problem with the ECC 6.0 web service.
    Cheers,
    Madhu

  • Not receiving MQ custom header (PutDateTime) in OSB Proxy service using MQ

    Hi,
    I am using OSB 11g and Websphere MQ version 7.0.
    I am trying to get PutDateTime header of message which is being polled from MQ through OSB proxy service using MQ transport.
    While logging inbound variable i found out that except this put date time header i am getting all other headers.
    Please suggest me something to get this header also.
    Regards,
    Naveen

    Hi Anuj,
    I am using OSB 11.1.0.3 version.
    By MQ client libraries, do you mean com.ibm.mq jar? i have this jar file put in lib section of my OSB home.
    Its really happening like when i am trying to log inbound variable for MQ request headers i am not getting put date time in that.
    ####<Sep 23, 2011 1:40:34 PM IST> <Error> <ALSB Logging> <wcrbtcsinbom222> <AdminServer> <[ACTIVE] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <647137b87487c06a:2875c7c7:13290bb7c1c:-8000-000000000000238b> <1316765434885> <BEA-000000> < [RouteToJMSQueue, null, null, REQUEST] inbound>>>>>>>>>>>>>>>: <con:endpoint name="ProxyService$CSPSPrj$EBooking$ProxyServices$AT_MQFrontRunner" xmlns:con="http://www.bea.com/wli/sb/context">
    <con:service/>
    <con:transport>
    <con:uri>mq://CSPS_GCS_DEV_TST?conn=CSPSPrj/EBooking/Utils/MQConnectionResource</con:uri>
    <con:mode>request</con:mode>
    <con:qualityOfService>exactly-once</con:qualityOfService>
    <con:request xsi:type="mq:MQRequestMetaData" xmlns:mq="http://www.bea.com/wli/sb/transports/mq" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
    <tran:headers xsi:type="mq:MQRequestHeaders" xmlns:tran="http://www.bea.com/wli/sb/transports">
    <mq:AccountingToken>FgEFFQAAACrQN1yT42JIgoumKNeOEgAAAAAAAAAAAAs=</mq:AccountingToken>
    <mq:ApplicationIdData></mq:ApplicationIdData>
    <mq:ApplicationOriginData></mq:ApplicationOriginData>
    <mq:BackoutCount>0</mq:BackoutCount>
    <mq:CharacterSet>1208</mq:CharacterSet>
    <mq:CorrelationId>AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA</mq:CorrelationId>
    <mq:Encoding>546</mq:Encoding>
    <mq:Expiry>-1</mq:Expiry>
    <mq:Feedback>0</mq:Feedback>
    <mq:Format>MQSTR</mq:Format>
    <mq:GroupId>AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA</mq:GroupId>
    <mq:MessageFlags>0</mq:MessageFlags>
    <mq:MessageId>QU1RIENTUFNfR0NTX0RFVsqwcE4gEaMC</mq:MessageId>
    <mq:MessageSequenceNumber>1</mq:MessageSequenceNumber>
    <mq:MessageType>8</mq:MessageType>
    <mq:Offset>0</mq:Offset>
    <mq:OriginalLength>-1</mq:OriginalLength>
    <mq:Persistence>0</mq:Persistence>
    <mq:Priority>0</mq:Priority>
    <mq:PutApplicationName>re MQ\java\jre\bin\javaw.exe</mq:PutApplicationName>
    <mq:PutApplicationType>11</mq:PutApplicationType>
    <mq:ReplyToQueueName></mq:ReplyToQueueName>
    <mq:ReplyToQueueManagerName>CSPS_GCS_DEV_QM</mq:ReplyToQueueManagerName>
    <mq:Report>0</mq:Report>
    <mq:UserId>SACRBTCSDEFR</mq:UserId>
    </tran:headers>
    </con:request>
    </con:transport>
    <con:security>
    <con:transportClient>
    <con:username>&lt;WLS Kernel></con:username>
    </con:transportClient>
    </con:security>
    </con:endpoint>>

  • Receiving the internal 500 error while testing java web service

    HI,
    Problem Summary:
    Receiving the internal 500 error while testing java web service in integrated weblogic server.
    my scenario is like,
    retrieve the Payload from Dehydration tables.
    We are connected to SOA_INFRA schema and we are retrieving the payload from the dehyadration tables based on InstanceId and ECID using Java Classes.After that i make it as a web service and i deployed in to intergrated weblogic Server.It is generating the Target End Point URI.When am i hitting this it is showing structure of the service.I am testing this service from soapUi it is returning the Server internal error with 500.Here i am passing inputs as InstanceId and ECID.
    I had verified in my Jdeveloper,Proxy settings are available.
    Error Payload:
    I am receiving the Internal 500 error because of JDeveloper HTTP Analyzer encountered an error retrieving: CONNECT https://192.168.0.41:9102 HTTP/1.0.
    An exception occurred while retrieving the response for https://192.168.0.41:9102.
    javax.net.ssl.SSLException: Connection has been shutdown: javax.net.ssl.SSLException: Unrecognized SSL message, plaintext connection?
         at com.sun.net.ssl.internal.ssl.SSLSocketImpl.checkEOF(SSLSocketImpl.java:1293)
         at com.sun.net.ssl.internal.ssl.AppInputStream.read(AppInputStream.java:65)
         at com.sun.net.ssl.internal.ssl.AppInputStream.read(AppInputStream.java:50)
         at oracle.jdevimpl.webservices.tcpmonitor.model.HttpMessageBase.readLine(HttpMessageBase.java:658)
         at oracle.jdevimpl.webservices.tcpmonitor.model.HttpRequest.read(HttpRequest.java:327)
         at oracle.jdevimpl.webservices.tcpmonitor.ConnectionHandler.getResponse(ConnectionHandler.java:405)
         at oracle.jdevimpl.webservices.tcpmonitor.ConnectionHandler.run(ConnectionHandler.java:331)
    Caused by: javax.net.ssl.SSLException: Unrecognized SSL message, plaintext connection?
         at com.sun.net.ssl.internal.ssl.InputRecord.handleUnknownRecord(InputRecord.java:523)
         at com.sun.net.ssl.internal.ssl.InputRecord.read(InputRecord.java:355)
         at com.sun.net.ssl.internal.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:798)
         at com.sun.net.ssl.internal.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1138)
         at com.sun.net.ssl.internal.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1165)
         at com.sun.net.ssl.internal.ssl.SSLSocketImpl.getSession(SSLSocketImpl.java:1916)
         at oracle.jdevimpl.webservices.tcpmonitor.ConnectionHandler.negotiateSSL(ConnectionHandler.java:707)
         at oracle.jdevimpl.webservices.tcpmonitor.ConnectionHandler.negotiateForwardedSSLConnection(ConnectionHandler.java:672)
         at oracle.jdevimpl.webservices.tcpmonitor.ConnectionHandler.run(ConnectionHandler.java:311

    An exception occurred while retrieving the response for https://192.168.0.41:9102.
    javax.net.ssl.SSLException: Connection has been shutdown: javax.net.ssl.SSLException: Unrecognized SSL message, plaintext connection?This error says that port 9102 is a plain HTTP port so either use the correct port (which is listening for HTTPS connections) or use HTTP instead of HTTPS in the URL.
    Regards,
    Anuj

  • Error while executing the proxy service

    Hi,
    I have a procedure which uses a database link to access my tables. And business service will invoke this procedure through JCA.
    We have created a datasource (Driver : non - XA for Service connections). However, while executing the proxy service it gives me below error.
    Do i need to change the type of driver. Can anybody please help me on this.
    <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
    <soapenv:Header xmlns:com1="com:gm:vehicleengineering:engineeringworkorder:ewostatus:types:ewostatusschema:1:0" xmlns:com="com:gm:common:utilities:types:servicecontrol:1:0">
    <com:ServiceControl>
    <com:Service>EWOStatus</com:Service>
    <com:Version>1.0</com:Version>
    <com:ConsumerID>CID</com:ConsumerID>
    <com:MessageID>MID</com:MessageID>
    <com:SentTimeStamp>2008-09-28T21:49:45</com:SentTimeStamp>
    </com:ServiceControl>
    </soapenv:Header>
    <soapenv:Body>
    <soapenv:Body>
    <com:ServiceFault xmlns:com="com:gm:common:utilities:types:servicefault:1:0">
    <com:FaultCode>SOAFLT-999</com:FaultCode>
    <com:FaultString>GeneralError</com:FaultString>
    <com:FaultActor>Server</com:FaultActor>
    <com:FaultDetail>Invoke JCA outbound service failed with connection error, exception: com.bea.wli.sb.transports.jca.JCATransportException: oracle.tip.adapter.sa.api.JCABindingException: oracle.tip.adapter.sa.impl.fw.ext.org.collaxa.thirdparty.apache.wsif.WSIFException: servicebus:/WSDL/VehicleEngineering/EngineeringWorkOrder/EWOStatus/V1/WSDL/jcaEWOStatus_1_0_0 [ GetEWOStatus_ptt::GetEWOStatus(InputParameters,OutputParameters) ] - WSIF JCA Execute of operation 'GetEWOStatus' failed due to: Interaction processing error.
    Error while processing the execution of the SP_GETEWOSTATUS API interaction.
    An error occurred while processing the interaction for invoking the SP_GETEWOSTATUS API. Cause: Exception [EclipseLink-4002] (Eclipse Persistence Services - 2.0.2.v20100323-r6872): org.eclipse.persistence.exceptions.DatabaseException
    Internal Exception: java.sql.SQLException: Internal error: Cannot obtain XAConnection java.lang.ClassCastException: oracle.jdbc.driver.T4CConnection
         at weblogic.jdbc.jta.DataSource.getXAConnectionFromPool(DataSource.java:1684)
         at weblogic.jdbc.jta.DataSource.getConnection(DataSource.java:439)
         at weblogic.jdbc.jta.DataSource.connect(DataSource.java:396)
         at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:355)
         at org.eclipse.persistence.sessions.JNDIConnector.connect(JNDIConnector.java:126)
         at org.eclipse.persistence.sessions.JNDIConnector.connect(JNDIConnector.java:94)
         at org.eclipse.persistence.sessions.DatasourceLogin.connectToDatasource(DatasourceLogin.java:162)
         at org.eclipse.persistence.internal.databaseaccess.DatasourceAccessor.connectInternal(DatasourceAccessor.java:327)
         at org.eclipse.persistence.internal.databaseaccess.DatabaseAccessor.connectInternal(DatabaseAccessor.java:295)
         at org.eclipse.persistence.internal.databaseaccess.DatasourceAccessor.reconnect(DatasourceAccessor.java:558)
         at org.eclipse.persistence.internal.databaseaccess.DatabaseAccessor.reconnect(DatabaseAccessor.java:1437)
         at org.eclipse.persistence.internal.databaseaccess.DatasourceAccessor.incrementCallCount(DatasourceAccessor.java:303)
         at oracle.tip.adapter.db.DBConnection.getTopLinkSQLConnection(DBConnection.java:335)
         at oracle.tip.adapter.db.transaction.DBTransaction.beginInternal(DBTransaction.java:126)
         at oracle.tip.adapter.db.sp.SPInteraction.executeStoredProcedure(SPInteraction.java:93)
         at oracle.tip.adapter.db.DBInteraction.execute(DBInteraction.java:248)
         at oracle.tip.adapter.sa.impl.fw.wsif.jca.WSIFOperation_JCA.performOperation(WSIFOperation_JCA.java:534)
         at oracle.tip.adapter.sa.impl.JCABindingReferenceImpl.request(JCABindingReferenceImpl.java:257)
         at com.bea.wli.sb.transports.jca.binding.JCATransportOutboundOperationBindingServiceImpl.invoke(JCATransportOutboundOperationBindingServiceImpl.java:150)
         at com.bea.wli.sb.transports.jca.JCATransportEndpoint.sendRequestResponse(JCATransportEndpoint.java:209)
         at com.bea.wli.sb.transports.jca.JCATransportEndpoint.send(JCATransportEndpoint.java:170)
         at com.bea.wli.sb.transports.jca.JCATransportProvider.sendMessageAsync(JCATransportProvider.java:572)
         at sun.reflect.GeneratedMethodAccessor771.invoke(Unknown Source)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:597)
         at com.bea.wli.sb.transports.Util$1.invoke(Util.java:83)
         at $Proxy142.sendMessageAsync(Unknown Source)
         at com.bea.wli.sb.transports.LoadBalanceFailoverListener.sendMessageAsync(LoadBalanceFailoverListener.java:152)
         at com.bea.wli.sb.transports.LoadBalanceFailoverListener.sendMessageToServiceAsync(LoadBalanceFailoverListener.java:603)
         at com.bea.wli.sb.transports.TransportManagerImpl.sendMessageToService(TransportManagerImpl.java:560)
         at com.bea.wli.sb.transports.TransportManagerImpl.sendMessageAsync(TransportManagerImpl.java:426)
         at com.bea.wli.sb.pipeline.PipelineContextImpl.dispatch(PipelineContextImpl.java:501)
         at stages.routing.runtime.RouteRuntimeStep.processMessage(RouteRuntimeStep.java:128)
         at com.bea.wli.sb.stages.StageMetadataImpl$WrapperRuntimeStep.processMessage(StageMetadataImpl.java:346)
         at com.bea.wli.sb.pipeline.RouteNode.doRequest(RouteNode.java:106)
         at com.bea.wli.sb.pipeline.Node.processMessage(Node.java:67)
         at com.bea.wli.sb.pipeline.PipelineContextImpl.execute(PipelineContextImpl.java:922)
         at com.bea.wli.sb.pipeline.Router.processMessage(Router.java:214)
         at com.bea.wli.sb.pipeline.MessageProcessor.processRequest(MessageProcessor.java:99)
         at com.bea.wli.sb.pipeline.RouterManager$1.run(RouterManager.java:591)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
         at com.bea.wli.sb.security.WLSSecurityContextService.runAs(WLSSecurityContextService.java:55)
         at com.bea.wli.sb.pipeline.RouterManager.processMessage(RouterManager.java:590)
         at com.bea.wli.sb.transports.TransportManagerImpl.receiveMessage(TransportManagerImpl.java:375)
         at com.bea.wli.sb.transports.CoLocatedMessageContext$1.run(CoLocatedMessageContext.java:164)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
         at weblogic.security.Security.runAs(Security.java:61)
         at com.bea.wli.sb.util.security.SecurityUtils.runAs(SecurityUtils.java:58)
         at com.bea.wli.sb.transports.CoLocatedMessageContext.send(CoLocatedMessageContext.java:157)
         at com.bea.wli.sb.transports.http.wls.HttpTransportProvider.sendMessageAsync(HttpTransportProvider.java:215)
         at sun.reflect.GeneratedMethodAccessor771.invoke(Unknown Source)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:597)
         at com.bea.wli.sb.transports.Util$1.invoke(Util.java:83)
         at $Proxy122.sendMessageAsync(Unknown Source)
         at com.bea.wli.sb.transports.LoadBalanceFailoverListener.sendMessageAsync(LoadBalanceFailoverListener.java:152)
         at com.bea.wli.sb.transports.LoadBalanceFailoverListener.sendMessageToServiceAsync(LoadBalanceFailoverListener.java:603)
         at com.bea.wli.sb.transports.TransportManagerImpl.sendMessageToService(TransportManagerImpl.java:560)
         at com.bea.wli.sb.transports.TransportManagerImpl.sendMessageAsync(TransportManagerImpl.java:426)
         at com.bea.wli.sb.pipeline.PipelineContextImpl.dispatch(PipelineContextImpl.java:501)
         at stages.routing.runtime.RouteRuntimeStep.processMessage(RouteRuntimeStep.java:128)
         at com.bea.wli.sb.stages.StageMetadataImpl$WrapperRuntimeStep.processMessage(StageMetadataImpl.java:346)
         at com.bea.wli.sb.pipeline.RouteNode.doRequest(RouteNode.java:106)
         at com.bea.wli.sb.pipeline.Node.processMessage(Node.java:67)
         at com.bea.wli.sb.pipeline.PipelineContextImpl.execute(PipelineContextImpl.java:922)
         at com.bea.wli.sb.pipeline.Router.processMessage(Router.java:214)
         at com.bea.wli.sb.pipeline.MessageProcessor.processRequest(MessageProcessor.java:99)
         at com.bea.wli.sb.pipeline.RouterManager$1.run(RouterManager.java:591)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
         at com.bea.wli.sb.security.WLSSecurityContextService.runAs(WLSSecurityContextService.java:55)
         at com.bea.wli.sb.pipeline.RouterManager.processMessage(RouterManager.java:590)
         at com.bea.wli.sb.transports.TransportManagerImpl.receiveMessage(TransportManagerImpl.java:375)
         at com.bea.wli.sb.transports.http.generic.RequestHelperBase$1.run(RequestHelperBase.java:152)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
         at com.bea.wli.sb.transports.http.generic.RequestHelperBase.securedInvoke(RequestHelperBase.java:151)
         at com.bea.wli.sb.transports.http.wls.HttpTransportServlet.service(HttpTransportServlet.java:127)
         at weblogic.servlet.FutureResponseServlet.service(FutureResponseServlet.java:25)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:821)
         at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
         at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:300)
         at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.doIt(WebAppServletContext.java:3686)
         at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3650)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
         at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2174)
         at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1446)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    Thanks,
    Chandana

    Make sure that you are using non-xa datasources and in DBAdapter outbound connection pool configuration provide the data source JNDI in "dataSourceName" property instead of "xADataSourceName" property. Update the DBAdapter after changing configuration.
    Regards,
    Anuj

  • "RABAX" occurs on server side error while testing asynchoronous web service

    I got error while testing asynchronous web service in WS navigator. I have created asynchronouse web service using RFC. Then I configured it in SOAMANAGER. When I tested it, got error "RABAX occurs on server side". Also I got dump in ST22. It is 'UNCHAUGHT_EXCEPTION - CX_SOAP_SEQ_SCD_ERROR'.
    I have tested for synchronous web service it works fine.  I found a difference in both web service WSDL file for below parameters value -
    commit
    blocking
    transaction
    wsrm
    I tried different way .. but no solution .. Plz suggest if someone have any idea.....Its very helpfull....

    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)

  • Cannot Test this Web Service using the Test Page

    Hello,
    I'm using
    - JDeveloper 11.1.1.3.0
    - SOA Suite 11.1.1.3.0
    - Weblogic Server 10.3.3
    - Windows XP SP3 (german version)
    Now I'm having a BPEL-Process (SOA) Project created in JDeveloper and deployment to the server works fine, i.e. the service can be seen in enterprise manager.
    But if I want to test the service using the webservice tester it get the following error if I copy the URL for getting the WSDL file to another browser tab:
    Cannot Test this Web Service using the Test Page
    Endpoint Name : FabricProvider (Service Description)
    You can test the Web Service using a Java client.
    Failed to Load a composite for composite identified by default/ReisebuchungService!1.0*soa_6aebb5fb-7830-497b-b853-839518d112f0
    Please verify that the composite has been deployed.
    Can you help me with this issue? I have no idea where to start debugging or resolving the problem.
    Thanks in advance

    Heya
    others and I face the same issue, reported here:
    TP4: Cannot Test this Web Service ...
    Oracle is not too responsive on the issue though.... :(
    Cheers Christian.

  • Rollback fault thrown while invoking a Proxy Service

    Hi,
    I am getting strange problem while invoking a proxy service.
    the operation on the service takes a list of customer numbers in the input.
    When the number of customer numbers is 10-20 it works fine but when I increase the customer numbers in the list to 200 it starts failing with the below error.
    *<<BaseCubeSessionBean::logError > Error while invoking bean "cube delivery": Rollback fault thrown.
    The current JTA transaction is aborting due to an user rollback fault being thrown from the BPEL code.
    This exception was caused by a bpelx:rollback fault being thrown. The user had directed the BPEL engine to roll back the current JTA transaction.
    There is no action recommended.
    ORABPEL-02180
    Rollback fault thrown.
    The current JTA transaction is aborting due to an user rollback fault being thrown from the BPEL code.
    This exception was caused by a bpelx:rollback fault being thrown. The user had directed the BPEL engine to roll back the current JTA transaction.
    There is no action recommended.*
    The cause for this error is as below
    javax.ejb.EJBException: Transaction Rolledback.: weblogic.transaction.internal.TimedOutException: Transaction timed out after 302 seconds
    I am clueless why the service is behaving different in both the cases.
    the endpoint of the webservice is the same in both the case and below is the sample request which I am sending.
    <v001:CustomerRequest>
    <v0011:CustomerNumberList>
    <v0011:CustomerNumber>12802582</v0011:CustomerNumber>
    <v0011:CustomerNumber>612391615</v0011:CustomerNumber>
    <v0011:CustomerNumber>189322879</v0011:CustomerNumber>
    <v0011:CustomerNumber>251524232</v0011:CustomerNumber>
    <v0011:CustomerNumber>208522415</v0011:CustomerNumber>
    <v0011:CustomerNumber>812603453</v0011:CustomerNumber>
    <v0011:CustomerNumber>12068921</v0011:CustomerNumber>
    <v0011:CustomerNumber>252053284</v0011:CustomerNumber>
    <v0011:CustomerNumber>191672097</v0011:CustomerNumber>
    <v0011:CustomerNumber>248131656</v0011:CustomerNumber>
    <v0011:CustomerNumber>8513869</v0011:CustomerNumber>
    </v0011:CustomerNumberList>
    <!--Optional:-->
    <v001:SynchToA>false</v001:SynchToA>
    <!--Optional:-->
    <v001:SynchToB>false</v001:SynchToB>
    <!--Optional:-->
    <v001:SynchToC>false</v001:SynchToC>
    <!--Optional:-->
    <v001:SynchToR>true</v001:SynchToR>
    </v001:CustomerRequest>
    Can anybody provide any pointers please... :|

    Hi-
    Can you try by increasing your JTA time out parameter, it seems to be a time out exception not sure if this could fix the issue. Anyways give a try and let us know the result.
    To increase the JTA parameter login to console --> Home --> Click on Domain under Domain Configuration -- > JTA and set the parameter Timeout Seconds to 1000 and then give a try.
    Let us know the result

  • What is the use of creating proxy services using WSDL.

    Hi
    Am a beginner in ALSB and i have a basic question. Business services are created using WSDL,thats sounds logical as we need to invoke the actual backend services .
    Proxy services are connected to business services and what is the need that it can be e created using WSDL.
    What is the use of creating proxy services using WSDL.

    Hi,
    I beleive you are confused because of the apparent inclusion of transport information in WSDL (that is the host:port/endpoint where the service is hosted). However, if you refer to the w3c specification of WSDL1.0 ([url http://www.w3.org/TR/wsdl]www.w3.org/TR/wsdl), you will find that WSDL has three separate sections:
    1. The schema information that describes data element(s): specified in types
    2. The message information ie message and port sections that specify the parameters and the operations
    3. The service section that specify the actual protocol and endpoint binding.
    Ideally, a WSDL can be broken down into these three separate components. Any WSDL containing the first two is called an abstract WSDL and is used for a top-down approcah for web services, and if the third part is used, then you get a concrete WSDL, containing invocation end-point also.
    Comming back to your question one can typically use an Abstract WSDL for creating proxy service. This way, the service requester and integration can go on two separate threads where the common denominator or agreement between these two parties in terms of operation name and data element are imposed using the WSDL.
    Thanks and Regards
    Vivek Nandey
    BEA Certified Developer for Integration Solutions

  • Error while testing External Web Service Integration

    I'm getting an error when I try to test an external webservice from Studio. After performing the steps to create an external webservice integration with SOAP, When I right-click on the .wsid file and choose "Test Service Operations" and chose the communication scenario and submit request, I get an error "A technical error error occured AP-RC-BDS-WS".
    I'm not able to call the service visa the ABSL script as well. When I debug, I get an error in the response CommFault as,
    "SoapfaultCode: 5 Server Error."
    I'm able to successfully test the web service from SOAPUI.
    Regards,
    Srikanth

    import ABSL;
    var Request: Library::AccProfExWebServInt.ZSI_Acc_Prof_Req_Obj.Request;
    var Response: Library::AccProfExWebServInt.ZSI_Acc_Prof_Req_Obj.Response;
    Request.ZMT_Acc_Prof_Req_obj.BUSINESS_GROUP = this.BusinessGroup;
    Request.ZMT_Acc_Prof_Req_obj.ZONE = this.Zone;
    Request.ZMT_Acc_Prof_Req_obj.REPRESENTATIVE = this.Representative;
    Request.ZMT_Acc_Prof_Req_obj.FROM_DATE = this.DateRange.StartDate.ToString();
    Request.ZMT_Acc_Prof_Req_obj.TO_DATE = this.DateRange.EndDate.ToString();
    Request.ZMT_Acc_Prof_Req_obj.REPORT_TYPE = this.ReportType;
    Request.ZMT_Acc_Prof_Req_obj.PROJS = this.Projects.ToString();
    Request.ZMT_Acc_Prof_Req_obj.SPECS = this.Specs.ToString();
    Request.ZMT_Acc_Prof_Req_obj.SALES_CALL = this.SalesCalls.ToString();
    Request.ZMT_Acc_Prof_Req_obj.TRAINING_ACTS = this.Training.ToString();
    //var Response = Library::AccProfExWebServInt.ZSI_Acc_Prof_Req_Obj(Request, " ", "AccountProfileScenario");
    Response = Library::AccProfExWebServInt.ZSI_Acc_Prof_Req_Obj(Request, "", "AccountProfileScenario");
    var CommFault = Response.CommunicationFault;
    var CommFaultItem = CommFault.Item;
    //Display Errors if any and return
    foreach (var item in CommFaultItem){
    raise MsgCommunicationFault.Create("E");
    return;
    //Display success message
    var ResponseUUID = Response.ZMT_Acc_Prof_Res_obj.EV_RESULT;
    raise MsgExternalResponse.Create("S");

  • JMS Biz & Proxy Services Using OSB & SSL

    We have a potential requirement being enforced upon us which states that our communication to another system using a JMS proxy service should be using SSL.
    Has anyone done this before using OSB?
    There is a "Use SSL" tick box on the proxy and business services, but I think this is purely for authentication and not transport - but I could be wrong as its not an area I know that much about.
    We're pushing for an IPSEC VPN link as that makes much more sense, but in the meantime I thought I'd ask if anyone had done any JMS + SSL work using OSB.
    Thanks,
    Pete

    Manoj, Thanks for your reply.
    Actually the other system is OSB!!
    It's a government system we're talking to but in the interests of open-ness, we cannot use OSB->OSB out of the box interfaces such as SAF etc, as that isn't an open enough interface and users of the interface who don't have OSB may be disadvantaged! Something like that anyway! SAF would be a perfect option for this interface, but .....
    What we've been so far is that all communication via JMS must be SSL based. But - t3s is not supported on this interface, so the SSL negotiation must be handled by a hardware device or something else.
    We think we've found BigIP load balancers do the job, but that's a large cost as we don't have those in our current infrastructure.
    We don't have much SSL communication apart from https, so I don't have a whole lot of experience with it and I just wondered if there was any OSB feature I'm missing, or something you can do in plan java code to get JMS communicating via SSL.
    Pete
    ps:A standard IPSEC VPN would do the job too, which we're going to try to push for, then, you just use the jms:// url to an address and the security is via the VPN.

  • OSB: Proxy service used in the WSDL address hostname, I want to use IP

    Hi all,
    I have a proxy service , open the WSDL address is as follows :
    ==============================================================================================
    <?xml version="1.0" encoding="UTF-8"?>
    <s0:definitions name="GeneralInboundServiceDefinitions" targetNamespace="http://nc.sgcc.edb.inbound" xmlns:s0="http://schemas.xmlsoap.org/wsdl/" xmlns:s1="http://www.iec.ch/TC57/2008/schema/message" xmlns:s2="http://nc.sgcc.edb.inbound" xmlns:s3="http://schemas.xmlsoap.org/wsdl/soap/">
    <s0:types>
    <schema xmlns="http://www.w3.org/2001/XMLSchema" xmlns:ns="http://www.iec.ch/TC57/2008/schema/message" xmlns:s1="http://nc.sgcc.edb.inbound" xmlns:s2="http://schemas.xmlsoap.org/wsdl/soap/">
    <import namespace="http://www.iec.ch/TC57/2008/schema/message" schemaLocation="http://10.118.59.85:7001/zxpt/services/GeneralInboundProxyService?SCHEMA%2Fhbdwzxpt%2FgeneralServices%2FResource%2FXSD%2FGeneralInboundService0"/>
    </schema>
    </s0:types>
    <s0:message name="invokeDataService">
    <s0:part element="s1:RequestMessage" name="parameters"/>
    </s0:message>
    <s0:message name="invokeDataServiceResponse">
    <s0:part element="s1:ResponseMessage" name="parameters"/>
    </s0:message>
    <s0:portType name="GeneralInbound">
    <s0:operation name="invokeDataService" parameterOrder="parameters">
    <s0:input message="s2:invokeDataService"/>
    <s0:output message="s2:invokeDataServiceResponse"/>
    </s0:operation>
    </s0:portType>
    <s0:binding name="GeneralInboundServiceSoapBinding" type="s2:GeneralInbound">
    <s3:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
    <s0:operation name="invokeDataService">
    <s3:operation style="document"/>
    <s0:input>
    <s3:body parts="parameters" use="literal"/>
    </s0:input>
    <s0:output>
    <s3:body parts="parameters" use="literal"/>
    </s0:output>
    </s0:operation>
    </s0:binding>
    <s0:service name="GeneralInboundServiceSoapBindingQSService">
    <s0:port binding="s2:GeneralInboundServiceSoapBinding" name="GeneralInboundServiceSoapBindingQSPort">
    <s3:address location="*_http://edb-8163dd8b4cb:7001/zxpt/services/GeneralInboundProxyService_*"/>
    </s0:port>
    </s0:service>
    </s0:definitions>
    ===============================================================================================
    The WSDL location is "http://edb-8163dd8b4cb:7001/zxpt/services/GeneralInboundProxyService", URL is used in the HOSTNAME, I want to return the IP OSB
    Kindly Help
    Thanks
    ptwen

    Please refer -
    How to get ip number in WSDL instead of host name?
    Why do you want to have IP instead of host name?
    Regards,
    Anuj

  • OSB - Accessing Operational Settings within Proxy Service

    Does anyone know if it is possible to access Operation Settings from within a Proxy Service?
    The use case is instead of logging, we perform auditing by inserting into a database. In certain environments, we would like to turn this off. I would like to reuse the Logs logging level field to decide whether or not to audit.
    So the message flow would have if (auditLevel = 'Warning') then BusinessService callout for auditing.
    Doing it this way lets operations choose whether or not to audit, instead of making code changes in different environments to choose whether or not to audit.

    Few months back I was also working on a similar requirement where client did not want to go for OSB configuration change (and even update) for changing the log levels or start auditing. After researching a little bit, we implemented java callout which used to read a property file and provide the value of auditing flag at runtime. We also created a java utility which used to clear the cache of server (because server loads & caches the property file after each restart). So whenever we have to make a change in auditing flag, we just change the value in property file and clear the cache of the server. This makes the fresh copy of property file available in server cache and OSB java callout picks the same.
    It was quite complex but the only better solution we could find. Please let us know if you get something better.
    Regards,
    Anuj

  • Osb - bind error handler to proxy service

    Hi!
    I have got a proxy service which polls a POP3 server to download emails and process them.
    My question: How could I bind an error handler to proxy service for noticing when the POP3 server is not available?
    So I would like to put an alert when the OSB looses the connection to email server. I tried to put an error handler to top component on message flow but it doesn't work...
    Could anyone help me?
    Thanks!
    Viktor

    For poller transports (email/File/FTP etc) it is not possible to catch errors of transport layer, in your service error handler. Re: OSB - Error Handler in FTP Transport for TransportException
    Thanks
    Manoj
    Edited by: Manoj Neelapu on Jun 28, 2010 3:51 PM

Maybe you are looking for