Webservice: No endpoints found

Hi gurus!
I'm not sure on witch forum to post this thread... so here goes...
I'm trying to create a webservice for an RFC function module (ZBAPI_HELLO_WORLD). I've already tried some manuals like http://help.sap.com/saphelp_nw70/helpdata/EN/0d/2eac5a56d7e345853fe9c935954ff1/content.htm, step by step, apparently everything works fine.
I go to SOAMANAGER, Web Service Administrator, select the service, verify that the endpoint is created, and everything seems OK.
However, I go to WSNAVIGATOR, enter the webservice (http://sapdes.bel.com.ve:8000/sap/bc/srt/rfc/sap/ZBAPIHELLOWORLD?sap-client=200&wsdl=1.1), but when I try to test it, I get the following error: No endpoints found for this Web service
I've tried deleting it and creating it again, and again, but so far nothing works, still the same error...
Am I missing something? some step I haven't seen?
Basically I'm using transactions SE37 to create the WS, and SOAMANAGER to test it, nothing more...
Appreciate any help!
Jesus

Hi... I'm working on ECC 6.0, so transactions WSADMIN and WSCONFIG are not available, instead I use transaction SOAMANAGER.
I checked note 1113162, but my system already has the SP level where the note was distributed, so it's already applied.

Similar Messages

  • Web Service Error - no service endpoints found

    Hi,
    I tried to create a web service deployable proxy project to consume an external third party web service url. There were no files generated for Logical Ports and Proxy Classes, though there are files generated for WSDL and SEIs. A further test on http://ip:port/index.html -> web service -> Enter the WSDL URL of the Web service -> No Service Endpoints Found, prove that something wrong with the url. 
    Any idea for me to check what goes wrong with the web service url? or could it due to firewall?

    In the meantime, there are also consuming my java-created web service using the test tool from http://www.soapclient.com/soaptest.html.
    Error given as below, from the
    wsse:InvalidSecurity0012BF1423AB0047000000350000065C00041741F13F5CDC : Found 0 operation definitions using keys: Key name:'first-body-element-ns' key value:'urn:EMMWSWsd'; Key name:'SoapRequestWrapper' key value:'sendMOtext'; 0012BF1423AB0047000000350000065C00041741F13F5CDC : Found 0 operation definitions using keys: Key name:'first-body-element-ns' key value:'urn:EMMWSWsd'; Key name:'SoapRequestWrapper' key value:'sendMOtext';
    From my application log, error shown as below:
    #1.5#0012BF1423AB0047000000360000065C00041741F13F5DA5#1151471894671#com.sap.security.core.server.ws.service.ServerSecurityProtocol#sap.com/AdapterWSTabEAR#com.sap.security.core.server.ws.service.ServerSecurityProtocol.handleRequest#J2EE_GUEST#230####800311f0066511dba3770012bf1423ab#SAPEngine_Application_Thread[impl:3]_5##0#0#Error#1#/System/Security/WS/SecurityProtocol#Java###An error occurred while processing the message security. Reason: . See trace entry .#3#com.sap.engine.interfaces.webservices.runtime.OperationNotFoundException#Found 0 operation definitions using keys: Key name:'first-body-element-ns' key value:'urn:EMMWSWsd'; Key name:'SoapRequestWrapper' key value:'sendMOtext'; #[no trace for com.sap.security.core.server.ws.service.ServerSecurityProtocol (severity above PATH)]#
    #1.5#0012BF1423AB0049000000370000065C00041741F475BD3F#1151471948578#com.sap.security.core.server.ws.service.ServerSecurityProtocol#sap.com/AdapterWSTabEAR#com.sap.security.core.server.ws.service.ServerSecurityProtocol.handleRequest#J2EE_GUEST#230####a024a020066511db954d0012bf1423ab#SAPEngine_Application_Thread[impl:3]_9##0#0#Error#1#/System/Security/WS/SecurityProtocol#Java###An error occurred while processing the message security. Reason: . See trace entry .#3#com.sap.engine.interfaces.webservices.runtime.OperationNotFoundException#Found 0 operation definitions using keys: Key name:'first-body-element-ns' key value:'urn:EMMWSWsd'; Key name:'SoapRequestWrapper' key value:'sendMOtext'; #[no trace for com.sap.security.core.server.ws.service.ServerSecurityProtocol (severity above PATH)]#
    Anyone has any idea what's the rootcause of all the incompatibility?

  • No endpoints found for interface

    Hi All,
    I have the following scenario: RFC in the backend system (ECC 6.0 SP09 no EhP's) and PI 7.1 as an Integration Broker.
    I have imported the RFC into Enterprise Services Repository and done the necessary tasks to configure an Enterprise Service.
    After that I have published the Interface to the Services Registry, Testing the Interface in WSNavigator is working fine.
    I have imported the Enterprise Service into Web Dynpro as a model and when running the Web Dynpro application I am receiving the following error:
    com.sap.esi.esp.service.server.query.discovery.ExtendedServiceException: no endpoints found for interface TreeInformationQuery_Out
    defaultTrace:
    Caused by: com.sap.tc.webdynpro.model.webservice.exception.WSModelRuntimeException: Exception on creation of service metadata for web service mass config parameters service reference ID 'TreeInformationQuery_Out_FICSIT_BASIC' and application name 'demo.sap.com/ficsit~tree'. Check mass configuration has been done properly.
         at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.getOrCreateWsrService(WSModelInfo.java:522)
    Any idea's?
    Regards,
    Ridouan

    Hi Sergei,
    My backend system is ECC 6.0 SP9 (no EhP's) and therefore I can't use the trx SOAMANAGER.
    I have imported an RFC from the ECC system into the PI 7.1 Enterprise Services Repository (Builder) and then published the Service (from Sender Agreement) into Services Registry also on the PI 7.1 system.
    Testing the service in WS Navigator is working fine, I can see an endpoint here.
    Also testing the WSDL with third-party application is working fine.
    JAVA Web Dynpro is given me the error: no endpoints found for interface...
    Thanks again.
    Regards,
    Ridouan

  • Webservcie: No endpoints found

    Hi gurus!
    I'm new to WebServices....
    I'm trying to create a webservice for an RFC function module (ZBAPI_HELLO_WORLD). I've already tried some manuals like http://help.sap.com/saphelp_nw70/helpdata/EN/0d/2eac5a56d7e345853fe9c935954ff1/content.htm, step by step, apparently everything works fine.
    I go to SOAMANAGER, Web Service Administrator, select the service, verify that the endpoint is created, and everything seems OK.
    However, I go to WSNAVIGATOR, enter the webservice (http://sapdes.bel.com.ve:8000/sap/bc/srt/rfc/sap/ZBAPIHELLOWORLD?sap-client=200&wsdl=1.1), but when I try to test it, I get the following error: No endpoints found for this Web service
    I've tried deleting it and creating it again, and again, but so far nothing works, still the same error...
    Am I missing something? some step I haven't seen?
    Basically I'm using transactions SE37 to create the WS, and SOAMANAGER to test it, nothing more...
    Appreciate any help! 
    Jesus

    check your URL... it need to have the correct port number, WSDL version etc..
    http://<host_name>:<port_number>/sap/bc/soap/rfc
    [Refer to this link>>|http://help.sap.com/saphelp_47x200/helpdata/en/2d/64d01de74911d6b2e400508b6b8a93/content.htm]

  • No endpoints found

    Hi,
    in the soamanager the webservice has an endpoint but anyway a I get this message
    Web Service Navigator.
    I am entering the WSDL URL of the Web service and on testing I get the message
    No endpoints found for this Web service.
    Pls. help me in this matter
    Bye
    Sw

    check your URL... it need to have the correct port number, WSDL version etc..
    http://<host_name>:<port_number>/sap/bc/soap/rfc
    [Refer to this link>>|http://help.sap.com/saphelp_47x200/helpdata/en/2d/64d01de74911d6b2e400508b6b8a93/content.htm]

  • Error. in WS Navigator - no endpoints found for interface

    Dear Friends,
    I have created a new Enterprise Service Interface and implemented in ABAP.  After the implementation I used SOAMANAGER to create the endpoint and publish the service using WSPUBLISH to Service Registry.  When I tested this service from SOA Management application(SOAMANAGER), the endpoint is working very good, but when I am testing this service from Service Registry, it is now showing any endpoint in the 'Enter Input Parameters' Step.  Also when I am trying to search the Service by using 'Search by Logical Destination', it shows the Service and when I select it, it shows an error message, "no endpoints found for interface (<namespace>/document)<Service Interface Name>_Document".
    If some one knows about this issue, please advice me to do next steps.
    Also I am planning to call this service from Visual Composer, I have configured the two logical destinations over there, also the service registry, even though, when i am searching the service, it shows an error like "Could not complete search".  
    Please advice me for the above issue also.
    Thanks in advance
    Vipindas

    Hi,
    If you have configured and tested from SOAMANAGER (which opens WSnavigator) then it is configured correctly. May be you are using wrong WSDL address.
    Copy url of wsdl from SOAMANGER test screen and use it directly in WSnavigator for testing.
    Regarding publishing of service WSPUBLISH should be able to publish correct service into service registry, but if for any reason it is not working then you can "publish" it directly from service registry by using publish option and provide url of wsdl from above option.
    If for any reason VC is unable to search service registry then create destination template for your every service by providing WSDL and use it in VC.
    Regards,
    Gourav

  • Stateless EJB Webservices vs Endpoint.publish() API for a production system

    Hello,
    I am currently designing an SOA JEE application using JAX-WS Webservices for the synchronous calls and JMS (MDB) for asynchronous access.
    It is packaged in a EAR containing one EJB module (no WAR), so I decided first to publish the Webservices using the javax.xml.ws.Endpoint.publish() method via the Spring org.springframework.remoting.jaxws.SimpleJaxWsServiceExporter. It's working very well and I can inject easily spring beans into my JAX-WS webservice, .. but :
    - I cannot see the published webservices in the Weblogic console
    - I have no idea on how the webservices instances are handled (just one ? )
    - Is it robust enough to be used in production in a critical financial application ?
    On the other hand, I just have to add a @Statless annotation to turn my JAX-WS classes into real EJB-Webservice aware, but it probably adds overhead in the Weblogic server and it's a bit more complicated to inject Spring resources.
    Any advice will help.
    Thanks
    GM

    Hi Kaustubh,
    A topic subscriber only receives messages that are published after it is registered with the topic. Your code for send() creates a publisher that sends the message to the topic before you create a new subscriber in your receive() code. Since that subscriber is created after your publisher has sent its message your subscriber will never receive this message!
    Your code will have the expected behaviour if you use a queue instead of a topic. If you have to use a topic, you could create your subscriber and your publisher in the init() method of your EJB and reuse them in your send() and receive() methods.
    Hope it helps.
    Best regards
    Arnaud Simon
    Arjuna Technologies - http://www.arjuna.com

  • Restful Webservice -- Page Not Found

    Using the web service wizard in SQL workshop, I have created a simple Restful web service using a GET request of Media Resource Type. The SQL statement gets the mime_type and a blob value from a table via an ID parameter. The code works fine in my standalone environment (apex 4.2 Listener 2.1) but on the Cloud, when I bind the variable :ID and press the test button, it always returns, "Page not Found". Even when I call the ws via APEX_WEB_SERVICE.MAKE_REST_REQUEST, it returns, "Page Not Found".
    The test screen creates the following URL: https://database-xxxxxx.us1.oraclecloudapps.com/apex/export/get/1
    If I run this in the browser, it also returns "Page Not Found". Looking at the URL, it doesn't look correct. Usually, the workspace is also a part of the url (after the /apex/ piece). Here it is missing. However, even when I add it, the error is still "Page Not Found". I have verified that the workspace has Restful web services enabled and I'm logging in with the admin user who has all three SQL Dev permissions granted.
    Has anyone seen this before? I'm I missing some permission or doing something wrong?
    Thanks,
    Steve

    Hi Steve,
    +> The code works fine in my standalone environment (apex 4.2 Listener 2.1)+
    Just to clarify things, Oracle Application Express Listener 2.0.1, which I assume is the version you have installed locally, is the latest Listener release available and is currently running on the Cloud. Oracle Application Listener 2.0 adds support for connecting to more than one database, and includes support for a number of different strategies for routing requests to the appropriate database, each of which is outlined in the Listener Installation and Configuration Guide (see http://docs.oracle.com/cd/E37099_01/doc/doc.20/e25066/config.htm#CBDCHGDF). All strategies rely on examining the request URI and choosing the database based on some kind of match against the URL, and depending on the chosen strategy, the URL will differ.
    +>... when I bind the variable :ID and press the test button, it always returns, "Page not Found".....The test screen creates the following URL: https://database-xxxxxx.us1.oraclecloudapps.com/apex/export/get/1+
    To assist in pinpointing the cause of the error you're seeing, could you please confirm whether the following details match your RESTful service:
    * URI Template: get/{id}
    * Resource Handler Method: GET
    * Resource Handler Source Type: Media Resource
    * Requires Secure Access: No
    * Source (matching the following syntax): select mime_type, blob_column from table_name where no = :id
    NOTE: if you need to set a bind variable for a parameter, then the "Set Bind Variables" option should be used instead of "Test".
    +> Usually, the workspace is also a part of the url (after the /apex/ piece).+
    In your local environment, the requests are being routed via the Path Prefix setting in the RESTful Service URL (see http://docs.oracle.com/cd/E37099_01/doc/doc.20/e25066/config.htm#CBDJIEGH). On your local instance, navigate to Administration > Manage Service, Set Workspace Preferences, and in the SQL Workshop region you'll find the Path Prefix item. The Path Prefix defaults to the short name of the workspace, which is what you're seeing in your URL locally. However, a different routing method is being used on the Cloud, so you will not see the Path Prefix used there.
    Would you mind testing the 'oracle.example.hr' sample RESTful Service in your workspace, and let me know if you experience issues running any of the examples?
    Regards,
    Hilary

  • Workshop WebService - Source file .jws not found

    Hi,
    I have developed WebService using BEA Weblogic Workshop 8.1. On my developement machine everything works perfectly. But when we build application (It is portal application with portal project - our corporate internet presentation and Webservice project with my WebService) using ant script exported from Workshop into ear and deploy it onto our testing servers WebService Doesn't work. When I try to call it I get this error message "Source file WebService.jws not found." When I add requested JWS file into its place, WebService starts to work as expected.
    Application is deployed from exploded directory which is created by unpacking EAR, this is to simplify patching of application and server is running in production mode.
    Any idea what is wrong?

    Hi,
    thank you very much. We have changed name of directory with exploded enterprise application to appname.ear and added -Dwlw.iterativeDev=false -Dwlw.testConsole=false -Dweblogic.jws.ProductionMode=true to java commandline and it works for now, don't know which change helped, but It works so I don't care.
    I tried these parameters before and it didn't work but I might have done some mistake so I was clueless.
    Thanks,
    Petr

  • Exception during call webservice from Web Dyn Pro application

    I receive exception when execute call to webservice. I found place where it fall, it is in stub classmdp\company\wd\_comp\src\packages\com\accenture\mdp\company\model\companybasic\proxies\Config1BindingStub.java
    in method below, in line
    this.transportBinding.call(this.stubConfiguration,this.globalProtocols,_getOperationProtocols("filterCompany"));
    public com.accenture.mdp.company.model.companybasic.proxies.types.p4.FilterCompanyResponse filterCompany(com.accenture.mdp.company.model.companybasic.proxies.types.p4.FilterCompany parameters) throws java.rmi.RemoteException,com.accenture.mdp.company.model.companybasic.proxies.Exception,com.accenture.mdp.company.model.companybasic.proxies.MDPException {
        try {
          super._beginLogFrame();
          // Operation input params initialization
          this.inputParams = new ServiceParam[1];
          this.inputParams[0] = new ServiceParam();
          this.inputParams[0].isElement = true;
          this.inputParams[0].schemaName = new QName("urn:CompanyServiceVi","filterCompany");
          this.inputParams[0].name = "parameters";
          this.inputParams[0].contentClass = com.accenture.mdp.company.model.companybasic.proxies.types.p4.FilterCompany.class;
          this.inputParams[0].content = parameters;
          // Operation output params initialization
          this.outputParams = new ServiceParam[1];
          this.outputParams[0] = new ServiceParam();
          this.outputParams[0].isElement = true;
          this.outputParams[0].schemaName = new QName("urn:CompanyServiceVi","filterCompanyResponse");
          this.outputParams[0].name = "parameters";
          this.outputParams[0].contentClass = com.accenture.mdp.company.model.companybasic.proxies.types.p4.FilterCompanyResponse.class;
          // Operation faults initialization
          this.faultParams = new ServiceParam[2];
          this.faultParams[0] = new ServiceParam();
          this.faultParams[0].isElement = true;
          this.faultParams[0].schemaName = new QName("urn:CompanyServiceWsd/CompanyServiceVi","filterCompany_java.lang.Exception");
          this.faultParams[0].name = "errorPart";
          this.faultParams[0].contentClass = com.accenture.mdp.company.model.companybasic.proxies.Exception.class;
          this.faultParams[1] = new ServiceParam();
          this.faultParams[1].isElement = true;
          this.faultParams[1].schemaName = new QName("urn:CompanyServiceWsd/CompanyServiceVi","filterCompany_com.accenture.mdp.common.exceptions.MDPException");
          this.faultParams[1].name = "errorPart";
          this.faultParams[1].contentClass = com.accenture.mdp.company.model.companybasic.proxies.MDPException.class;
          com.accenture.mdp.company.model.companybasic.proxies.types.p4.FilterCompanyResponse parametersTemp;
          this.transportBinding.setTypeMappingRegistry(this.typeRegistry);
          this.transportBinding.startOperation(this.inputParams,this.outputParams,this.faultParams);
          // Binding Context initialization
          this.bindingConfiguration.clear();
          bindingConfiguration.setProperty("soapAction","");
          bindingConfiguration.setProperty("style","document");
          bindingConfiguration.setProperty("transport","http://schemas.xmlsoap.org/soap/http");
          PropertyContext bindingConfigurationX;
          bindingConfigurationX = bindingConfiguration.getSubContext("output");
          bindingConfigurationX.setProperty("operationName","filterCompany");
          bindingConfigurationX.setProperty("use","literal");
          bindingConfigurationX = bindingConfiguration.getSubContext("input");
          bindingConfigurationX.setProperty("operationName","filterCompany");
          bindingConfigurationX.setProperty("use","literal");
          bindingConfigurationX.setProperty("parts","parameters");
          super._fillEndpoint(bindingConfiguration);
          _buildOperationContext("filterCompany",this.transportBinding);
          this.transportBinding.call(this.stubConfiguration,this.globalProtocols,_getOperationProtocols("filterCompany"));
          _setEndpoint((String) bindingConfiguration.getProperty(com.sap.engine.services.webservices.jaxrpc.wsdl2java.ClientTransportBinding.ENDPOINT));
          if (this.faultParams[0].content != null) {
            throw (com.accenture.mdp.company.model.companybasic.proxies.Exception) this.faultParams[0].content;
          if (this.faultParams[1].content != null) {
            throw (com.accenture.mdp.company.model.companybasic.proxies.MDPException) this.faultParams[1].content;
          parametersTemp = (com.accenture.mdp.company.model.companybasic.proxies.types.p4.FilterCompanyResponse) this.outputParams[0].content;
          return parametersTemp;
        } catch (com.accenture.mdp.company.model.companybasic.proxies.Exception e) {
          throw e;
        } catch (com.accenture.mdp.company.model.companybasic.proxies.MDPException e) {
          throw e;
        } catch (javax.xml.rpc.soap.SOAPFaultException e) {
          throw e;
        } catch (java.lang.Exception e) {
          throw new RemoteException("Service call exception",e);
        } finally {
          super._endLogFrame("filterCompany");
    I receive Service call exception; nested exception is: java.lang.NullPointerException
    May be anybody could suggest me how can I get more information about of  reason of this exceprion ?
    How to repair it ?

    Check the following path in your server:
    If you are using NW04s: :\usr\sap\<InstanceName>\JC00\j2ee\cluster\server0\log\
    If you are using CE: :\usr\sap\<InstanceName>\J00\j2ee\cluster\server0\log.
    If you are using CE: [Log Viewing with the SAP MC|http://help.sap.com/saphelp_nwce10/helpdata/en/44/f71b59e38e2462e10000000a1553f7/content.htm]
    Bala

  • How to configure the connection WebService for ERP?

    Hi Experts,
    I need professional help.
    I will development the Webservice in the NWDS(Composite Application).
    1.The development of the WebService in NWDS.
    2.The configure of the "Web Service  End Point URL" in NWA.
       (NWA->SOA Management-> Application and Scenario Communication->Single Service Administration->Consumer Proxies)
    I don't know "Web Service  End Point URL".
    We investigated the following URL as a reference.
    http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/b043ef4e-e8d1-2c10-7d88-8077b209ce55
    but it's WebService was not found to be SOA Manager
    What is needs in addition to the NWDS or SOA Manager ?
    Regards.
    Shinya

    Hi Vamshi.
    I tried to wsnavigator.
    but not completed wsnavigator.
    The returnmessage of the Webservice.
    "Invalid Response content type. Server returned code (500) with message <OK> and content type <text/html; charset=UTF-8>."
    Result Message
    <?xml version="1.0" encoding="utf-8"?>
    <SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
      <SOAP-ENV:Body>
        <SOAP-ENV:Fault>
          <faultcode>SOAP-ENV:Server</faultcode>
          <faultstring>Invalid Response content type. Server returned code (500) with message &lt;OK&gt; and content type &lt;text/html; charset=UTF-8&gt;.</faultstring>
          <detail>
            <ns3:CAFServiceException xmlns:ns3="http://www.sap.com/caf/sap.com/caf.core/faults" xmlns:ns2="http://www.sap.com/caf/demo.sap.com/test090102/modeled/PurchaseOrderCreate090103">
              <nestedStackTraceString>com.sap.caf.rt.exception.CAFServiceException: Invalid Response content type. Server returned code (500) with message &lt;OK&gt; and content type &lt;text/html; charset=UTF-8&gt;.&#13;
         at com.sap.demo.test090102.modeled.appsrv.purchaseordercreate090103.PurchaseOrderCreate090103Bean.purchaseOrderCreate090103(PurchaseOrderCreate090103Bean.java:45)&#13;
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)&#13;
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)&#13;
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)&#13;
         at java.lang.reflect.Method.invoke(Method.java:585)&#13;
         at com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:46)&#13;
         at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:166)&#13;
         at com.sap.engine.services.ejb3.runtime.impl.Interceptors_WS.invoke(Interceptors_WS.java:31)&#13;
         at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)&#13;
         at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext$InvocationContextImpl.proceed(AbstractInvocationContext.java:131)&#13;
         at com.sap.caf.rt.interceptors.LogInterceptor.aroundInvoke(LogInterceptor.java:61)&#13;
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)&#13;
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)&#13;
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)&#13;
         at java.lang.reflect.Method.invoke(Method.java:585)&#13;
         at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Application.invoke(Interceptors_Application.java:40)&#13;
         at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)&#13;
         at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatesTransition.invoke(Interceptors_StatesTransition.java:19)&#13;
         at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)&#13;
         at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Resource.invoke(Interceptors_Resource.java:71)&#13;
         at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)&#13;
         at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.doWorkWithAttribute(Interceptors_Transaction.java:38)&#13;
         at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.invoke(Interceptors_Transaction.java:22)&#13;
         at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)&#13;
         at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:189)&#13;
         at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatelessInstanceGetter.invoke(Interceptors_StatelessInstanceGetter.java:16)&#13;
         at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)&#13;
         at com.sap.engine.services.ejb3.runtime.impl.Interceptors_SecurityCheck.invoke(Interceptors_SecurityCheck.java:21)&#13;
         at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)&#13;
         at com.sap.engine.services.ejb3.runtime.impl.Interceptors_ExceptionTracer.invoke(Interceptors_ExceptionTracer.java:16)&#13;
         at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)&#13;
         at com.sap.engine.services.ejb3.runtime.impl.DefaultInvocationChainsManager.startChain(DefaultInvocationChainsManager.java:133)&#13;
         at com.sap.engine.services.ejb3.webservice.impl.DefaultImplementationContainer.invokeMethod(DefaultImplementationContainer.java:203)&#13;
         at com.sap.engine.services.webservices.espbase.server.runtime.RuntimeProcessingEnvironment.process0(RuntimeProcessingEnvironment.java:456)&#13;
         at com.sap.engine.services.webservices.espbase.server.runtime.RuntimeProcessingEnvironment.preProcess(RuntimeProcessingEnvironment.java:430)&#13;
         at com.sap.engine.services.webservices.espbase.server.runtime.RuntimeProcessingEnvironment.process(RuntimeProcessingEnvironment.java:232)&#13;
         at com.sap.engine.services.webservices.runtime.servlet.ServletDispatcherImpl.doPostWOLogging(ServletDispatcherImpl.java:156)&#13;
         at com.sap.engine.services.webservices.runtime.servlet.ServletDispatcherImpl.doPostWithLogging(ServletDispatcherImpl.java:96)&#13;
         at com.sap.engine.services.webservices.runtime.servlet.ServletDispatcherImpl.doPost(ServletDispatcherImpl.java:66)&#13;
         at SoapServlet.doPost(SoapServlet.java:51)&#13;
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)&#13;
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)&#13;
         at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:140)&#13;
         at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:37)&#13;
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:466)&#13;
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:291)&#13;
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:396)&#13;
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:385)&#13;
         at com.sap.engine.services.servlets_jsp.filters.DSRWebContainerFilter.process(DSRWebContainerFilter.java:48)&#13;
         at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)&#13;
         at com.sap.engine.services.servlets_jsp.filters.ServletSelector.process(ServletSelector.java:76)&#13;
         at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)&#13;
         at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:240)&#13;
         at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)&#13;
         at com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:78)&#13;
         at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)&#13;
         at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)&#13;
         at com.sap.engine.services.httpserver.filters.ResponseLogWriter.process(ResponseLogWriter.java:60)&#13;
         at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)&#13;
         at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)&#13;
         at com.sap.engine.services.httpserver.filters.DefineHostFilter.process(DefineHostFilter.java:27)&#13;
         at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)&#13;
         at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)&#13;
         at com.sap.engine.services.httpserver.filters.MonitoringFilter.process(MonitoringFilter.java:29)&#13;
         at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)&#13;
         at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)&#13;
         at com.sap.engine.services.httpserver.filters.MemoryStatisticFilter.process(MemoryStatisticFilter.java:43)&#13;
         at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)&#13;
         at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)&#13;
         at com.sap.engine.services.httpserver.filters.DSRHttpFilter.process(DSRHttpFilter.java:42)&#13;
         at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)&#13;
         at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)&#13;
         at com.sap.engine.services.httpserver.server.Processor.chainedRequest(Processor.java:425)&#13;
         at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.process(Processor.java:250)&#13;
         at com.sap.engine.services.httpserver.server.rcm.RequestProcessorThread.run(RequestProcessorThread.java:45)&#13;
         at com.sap.engine.core.thread.execution.Executable.run(Executable.java:109)&#13;
         at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:314)&#13;
    Caused by: javax.xml.ws.WebServiceException: Invalid Response content type. Server returned code (500) with message &lt;OK&gt; and content type &lt;text/html; charset=UTF-8&gt;.&#13;
         at com.sap.engine.services.webservices.espbase.client.jaxws.core.WSInvocationHandler.processTransportBindingCall(WSInvocationHandler.java:173)&#13;
         at com.sap.engine.services.webservices.espbase.client.jaxws.core.WSInvocationHandler.invokeSEISyncMethod(WSInvocationHandler.java:120)&#13;
         at com.sap.engine.services.webservices.espbase.client.jaxws.core.WSInvocationHandler.invokeSEIMethod(WSInvocationHandler.java:83)&#13;
         at com.sap.engine.services.webservices.espbase.client.jaxws.core.WSInvocationHandler.invoke(WSInvocationHandler.java:64)&#13;
         at $Proxy1928.purchaseOrderCreateRequestConfirmationIn(Unknown Source)&#13;
         at com.sap.demo.test090102.modeled.appsrv.purchaseordercreate090103.PurchaseOrderCreate090103Bean.purchaseOrderCreate090103(PurchaseOrderCreate090103Bean.java:33)&#13;
         ... 76 more&#13;
    Caused by: com.sap.engine.services.webservices.espbase.client.bindings.exceptions.TransportBindingException: Invalid Response content type. Server returned code (500) with message &lt;OK&gt; and content type &lt;text/html; charset=UTF-8&gt;.&#13;
         at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.handleSOAPResponseMessage(SOAPTransportBinding.java:535)&#13;
         at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.call_SOAP(SOAPTransportBinding.java:1085)&#13;
         at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.call_SOAP_Idenpotency(SOAPTransportBinding.java:796)&#13;
         at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.callWOLogging(SOAPTransportBinding.java:777)&#13;
         at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.call(SOAPTransportBinding.java:746)&#13;
         at com.sap.engine.services.webservices.espbase.client.jaxws.core.WSInvocationHandler.processTransportBindingCall(WSInvocationHandler.java:167)&#13;
         ... 81 more&#13;
    </nestedStackTraceString>
            </ns3:CAFServiceException>
          </detail>
        </SOAP-ENV:Fault>
      </SOAP-ENV:Body>
    </SOAP-ENV:Envelope>
    Regards.
    Shinya

  • Microsoft SQL 2005 WebServices - SOAP Result Parsing

    Hello,
    I have successfully connected to, sent a request and
    retrieved a SOAP response from, the WebServices functionality
    (ENDPOINT) using MS-SQL 2005. What I need to know how to do is
    parse the SOAP response in FLEX as to access the actual data for
    use in the application.
    How do I extract only the node that contains the data and
    then use this for binding my controls? I don't need any of the SOAP
    header stuff in there. Of course I could loop through the
    xyz.lastResult and parse onyl the parts I need to a new XML object,
    but that seems a lot of processing for something that is almost
    there.
    Any help would be appreciated.
    Sal

    quote:
    Originally posted by:
    TN_SGIA
    Hello,
    I have successfully connected to, sent a request and
    retrieved a SOAP response from, the WebServices functionality
    (ENDPOINT) using MS-SQL 2005. What I need to know how to do is
    parse the SOAP response in FLEX as to access the actual data for
    use in the application.
    Can you share the code to do that with me? I'm not good a
    SOAP requests, and this would be an excelent contribution to my
    project. Thank you.

  • Service Registry: why do i need two bindings (wsdlDeployment and endPoint)

    based on the technical note of Clemens Utschig "Enabling a Dynamic, Reusable SOA with Oracle BPEL Process Manager and Oracle Service Registry" i have one question:
    why do i need two bindings (wsdlDeployment and endPoint) in my service in the service registry. if i only define the wsdlDeployment if get this messages:
    <2006-12-07 09:39:02,559> <FATAL> <default.collaxa.cube.ws> no endpoint found - nothing to adjust
    <2006-12-07 09:39:02,559> <WARN> <default.collaxa.cube.ws> Could not lookup base endpoint!
    the problem of defining two bindings is that the url to my partner is redundant.

    Hi Clemens,
    The UDDI Version 3.0.2 Specification (http://www.uddi.org/pubs/uddi_v3.htm) say this:
    B.1.2 Using the "wsdlDeployment" value
    Instead of directly providing the network address in the accessPoint, it is occasionally useful or necessary to provide this information through indirect means. One common scenario for such a behavior is when the accessPoint is embedded within a WSDL file. In such a scenario, the UDDI accessPoint contains the address of the WSDL file, and the client then must retrieve the WSDL file and extract the end point address from the WSDL file itself.
    In this case, decorating the UDDI accessPoint with a useType="wsdlDeployment" is appropriate. A sample of such behavior is as follows:
    <bindingTemplate bindingKey="uddi:example.org:catalog">
       <description xml:lang="en">
           Browse catalog Web service
       </description>
       <accessPoint useType="wsdlDeployment">
           http://www.example.org/CatalogWebService/catalog.wsdl
       </accessPoint>
       <categoryBag>
           <keyedReference keyName="uddi-org:types:wsdl"
           keyValue="wsdlDeployment"
           tModelKey="uddi:uddi.org:categorization:types"/>
       </categoryBag>
    </bindingTemplate>In the example above, a client would be able to parse the result of the bindingTemplate and determine the end point of the Web service within the WSDL file discovered in the accessPoint element. Note that the bindingTemplate has also been categorized with the "wsdlDeployment" value from the uddi.org:categorization:types scheme so that it can be discovered through a find_binding API call.
    1) This means for me that providing one binding with useType=wsdlDeployment should be enough.
    2) Sadly the "Business Service Control" of the Service Registry (Publish new WSDL service) does not create the correct structure needed by the bpel-engine. The "Publish new WSDL service" wizard just creates one service with one binding with useType=other (http). So if i want to reuse this published service from bpel (as a service consumer) i have to switch to the "Service Registry Admin Control" and create a second binding with useType=wsdlDeployment. But i don't want the developers to get inside the "Service Registry Admin Control"! They should only work with the "Business Service Control".
    All this makes the usage of the service-registry very unhandy and reduce the acceptance for developers because of unnecessary manual steps and broken security principles.
    My wish for this issue is that the "Publish new WSDL service" inside the "Business Service Control" of the Service Registry would additionlly create this needed binding with useType=wsdlDeployment.
    Best Regards,
    Harald Reinmueller

  • Problem in JAXRPC Webservice - Urgent

    This is Santhakumar.
    I have developed and deployed a JAXRPC webservice in Tomcat5.0 with JWSDP1.5.
    WSDL is created and it works fine for normal java remote methods.
    But when I write a code for to connect a live server ( EPP-Extensible Provisioning Protocol TCP server ), I could not invoke the service.
    I get the following error:
    ================================================================
    C:\examples\jaxrpc\dynamicproxy>ant run
    Buildfile: build.xml
    run-client:
    [java] UrlString = http://localhost:8080/domain-jaxrpc/domain?WSDL
    [java] java.rmi.ServerException: JAXRPCSERVLET28: Missing port information
    [java] at com.sun.xml.rpc.client.StreamingSender._raiseFault(StreamingS
    ender.java:497)
    [java] at com.sun.xml.rpc.client.StreamingSender._send(StreamingSender.
    java:294)
    [java] at com.sun.xml.rpc.client.dii.CallInvokerImpl.doInvoke(CallInvok
    erImpl.java:79)
    [java] at com.sun.xml.rpc.client.dii.BasicCall.invoke(BasicCall.java:48
    2)
    [java] at com.sun.xml.rpc.client.dii.CallInvocationHandler.doCall(CallI
    nvocationHandler.java:121)
    [java] at com.sun.xml.rpc.client.dii.CallInvocationHandler.invoke(CallI
    nvocationHandler.java:85)
    [java] at $Proxy0.domainCheck(Unknown Source)
    [java] at dynamicproxy.DomainClient.main(Unknown Source)
    run:
    BUILD SUCCESSFUL
    Total time: 3 seconds
    C:\examples\jaxrpc\dynamicproxy>
    ===========================================================================
    I tried in many ways to resolve it.But still I could not find out any solutions.
    Is there any security settings to be handled for that?
    The method works fine and the server is connected  when I execute it from the normal java class in command prompt.
    But when implementing that method in JAXRPC webservice only I found this problem.
    Please share your ideas with me to resolve this problem.I am at urgent.
    Thanks in advance.
    Santhakumar.
    The sample example site used is:
    http://www.cis.umassd.edu/~hxu/Projects/UMD/WebServices/

    Please check the OSS note - 1041204 - Controlling COMMIT WORK in production order BAPIs
    Hope this helps you.

  • WebServices in the 'Oracle Integration Repository

    Recently we are upgraded to Oracle 11.5.10.2 and trying to integrate with our custom application using ‘WebServices’.
    I found couple of webservices in the ‘Oracle Integration Repository” list, which is at ‘http://irep.oracle.com/index.html’, But how to configure in Oracle 11.5.10.2 and expose/use/access those webservice’s from other IAS servers/Applications (like BizTalk).
    I will appreciate if any one helps me.
    Regards
    PathiTVB

    Hi;
    Please check below which could be helpful for your issue:
    API User Notes - HTML Format [ID 236937.1]
    R12.0.[3-4] : Oracle Install Base Api / Open Interface Setup Test [ID 427566.1]
    Pelase also check below:
    Api's in EBS
    Re: Api's in EBS
    http://sairamgoudmalla.blogspot.com/2009/05/script-to-find-oracle-apis-for-any.html
    API
    Fixed Asset API
    List of API
    Re: List of APIs
    Oracle Common Application Components API Reference Guide
    download.oracle.com/docs/cd/B25284_01/current/acrobat/jta115api.pdf
    Regard
    Helios

Maybe you are looking for

  • How to handle data in a request object

    I want to know the best way to handle data received from sql query to display on a jsp page and for page navigation. If I store data in a request object then the data is lost after displaying first page. When user hits Next link to view more data I n

  • Losing panels since last CS6 update

    I'm a Creative Cloud member who gets the updates to my software as soon they are available.  After the last update to CS6 (which I am still using to stay compatible with my coworkers who have not gotten CC yet), I've noticed that I'm randomly losing

  • Web module DC Not showing Differnt Objects

    hi all, We have created a web module DC on track in which we have a JSP page. we are able to access the JSP page from the browser. but we have kept an image,data file(xml) in the same directory as of JSP (webContent) which are not accessible. point t

  • RegEx to find "T-" literally

    I've been trying to find some help on writing regular expressions and haven't been very lucky. I'm trying to write a regular expression to find "T-" to use with REFind. Would the RegEx be \T- ?

  • HT1145 airport utility for windows

    How to manage Airport Extreme from Windows PC? How to connect at 300 Mbps? Which secuirty protocol to use to connect wireless N speed?