Web Service visible in WS navigator

I have developed web service and is deployed in to SAP EP (.PAR file). Iu2019m able to access wsdl through url and also able to access web services through our web service client but
This web service not listed in the WS navigator of SAP EP System
How can I make my WS visible in WS navigator?
All listed web services in WS Navigator are prompting for user name and password while testing
When I test my WS, it does not ask for authentication.
Regards,
Rasika

Hi capronero,
If the process is deployed it should also expose itself as a web service. The service will be published with the name of the service interface of your message start event. Simply click on the "Start" event in your process model and check the service interface name and the operation name. This should also be visibile in the WS navigator.
Cheers,
Martin

Similar Messages

  • Web services test using WS Navigator doesnot return field values

    Hi experts,
    We are running ECC 6 (NW 7 Ehp1) ABAP stack and NW CE 7.1 with Java stack (J2EE Engine 7.11). We are trying to test web services using WS Navigator. We can logon to WS Navigator and perform the test. The test shows a success return code, however, it doesn't bring back field values. We can see the values when we perform this test within ABAP stack. A sample of WS Navigator XML log for the service test is as below:
    <?xml version="1.0" encoding="utf-8"?>
    <soap-env:Envelope xmlns:soap-env="http://schemas.xmlsoap.org/soap/envelope/">
      <soap-env:Header/>
      <soap-env:Body>
        <n0:ZcGetCustomerInfoResponse xmlns:n0="urn:sap-com:document:sap:soap:functions:mc-style">
          <OKna1>
            <Mandt/>
            <Kunnr/>
            <Land1/>
            <Name1/>
            <Name2/>
            <Ort01/>
            <Pstlz/>
            <Regio/>
            <Sortl/>
    u2026
           <MessageV3/>
            <MessageV4/>
            <Parameter/>
            <Row>0</Row>
            <Field/>
            <System/>
          </Return>
        </n0:ZcGetCustomerInfoResponse>
      </soap-env:Body>
    </soap-env:Envelope>
    If someone can provide insight why is this happening, I would greatly appreciate it.
    Regards
    Nirmal

    Wondering if I posted this in the wrong forum. Can someone please guide me if it is the wrong forum for this question.
    Thanks
    Nirmal

  • Web Service Not Appearing in navigator after deployment

    have written some EJBs (Entity- and Session-Beans), created a WebService from the Session-Bean. After having deployed the WebService, which finished without error, the Web Service cannot be accessed by Web Service Navigator, nor by Visual Admin or Web Interface.
    Environment configuration:
    - SAP Web AS 6.40 SP9
    Can anybody help me, please ...

    Hi,
    Did you solve the issue ? I am facing the same issue.
    Can you please let me know whats missing
    Regards
    KG

  • Web service published but not visible

    Hi,
    I have developed a Webservice from a WSDL file i created from a XI outbound interface following the steps given in the thread below.
    /people/sap.user72/blog/2005/11/17/xi-how-to-publish-wsdl-generated-from-xi-to-uddi
    In the UDDI Client i got the message that the WS has been successfully published but i am not able to view my Web Service in the WS Navigator.
    What is the procedure to view a WS published using the UDDI client? is there any direct url to view the WS?

    This is the url inside my WSDL:
    http://cgnsap27:8000/sap/xi/engine?type=entry&version=3.0&Sender.Service=SATYAM_LSPM_BS&Interface=http%3A%2F%2Fsatyam.com%2Fxi%2FLSPM%5ELspm_SampleIdHelp_MI
    If i try the URL i get this :
    - <SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
      <SOAP:Header />
    - <SOAP:Body>
    - <SOAP:Fault xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
      <faultcode>SOAP:Client</faultcode>
      <faultstring>Empty HTTP request received</faultstring>
      <faultactor>http://sap.com/xi/XI/Message/30</faultactor>
    - <detail>
    - <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
      <SAP:Category>XIProtocol</SAP:Category>
      <SAP:Code area="MESSAGE">EMPTY_HTTP_REQUEST_RECEIVED</SAP:Code>
      <SAP:P1 />
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack>Empty HTTP query received. No message processing possible</SAP:Stack>
      </SAP:Error>
      </detail>
      </SOAP:Fault>
      </SOAP:Body>
      </SOAP:Envelope>
    But what i expect is a WS in the WS Navigator as i have already published the wsdl using the UDDI client.

  • MDM Web Service Generator - How to Call WS in Java?

    Hi there,
    I have generated a web service by navigating to http://<server>:<port>/mdm/wsgenerator - The web service is succesfully generated and deployed. I can easily test the web service using the WS Navigator (http://<server>:<port>/wsnavigator).
    I am now trying to use NWDS7.2 to create a wrapper web service, and need to call my generated MDM WS using Java code. I have created a CAF project, and imported the MDM web service using the WSDL. I have created an application service and no matter what I try, I cannot get the MDM web service to instantiate.
    Is there anyone that has done this before? What method should be used?
    All I need to know is how to create an instance of the generated MDM web service - There is no obvious constructor to use. See my code below, but this creates an exception at runtime for "IndexOutOfBoundsException". Note that the web service I generated is called "MdmWfProjectUpdate"
    service = new MdmWfProjectUpdateViDefaultService(
                                  new java.net.URL(
                                              "http://<server>:<port>/MdmWfProjectUpdate/HTTPBasic?wsdl"),
                                  new javax.xml.namespace.QName(
                                              "urn:MdmWfProjectUpdateWsd/HTTPNone", "MdmWfProjectUpdateVi_DefaultService"));
    I can call other web services without a problem in my code, so it is quite confusing that I cannot get this to work...
    Any help will be appreciated!

    Hi david ,
    When u imported  this webservice,there will be lot of classes generated .In these classes some are executable classes.Like if your webservice contain some operations like update,create,delete.
    then for each operation tere will be one executable class  generated.
    this class  must have some function like execute or invoke.You have to call this function in order to get the results.
    Just check whether is there any such class generated or not.
    Kindly revert back with your results.
    Thanks,
    sudhanshu

  • MDM Web Service authentication issue. How to use ?

    Hi,
    I' am a Microsoft technology person I' am working on integrating SAP MDM 7.1 to SharePoint 2010 using MDM Web Services interface and consuming the same in .NET custom component.
    I tried the WS with "None" authentication and it worked great.
    I' am having issues understanding how HTTPAuthentication with SAP Logon ticket authentication works in MDM.
    Created the authentication enabled web service and while testing in NetWeaver WS Navigator, it throws me exception, not able to establish session with repository for user XYZ.
    Please help me with the following queries I have:
    1) How to test a authentication enabled web service in NetWeaver WS Navigator ? Do the user id/password needs to be set in the "Invocation Parameters" ? Link to any article etc will be appreciated.
    2) How to pass the MDM user credentials (or just the username) in the MDM web service in .NET code. I didn't see any parameter in the Client class constructor to pass the same, nothing related to that found in the code that gets generated on adding the service reference.
    As per the documentation on the MDM security, looks like a trust relationship also needs to be configured on MDM - allow.ip file entries.
    However first I want to understand how to pass this information in Web Services through code.
    SharePoint   -
    (1)--> SAP PI  -(2)--
    > SAP MDM                                             
    (integrated with Active Directory                        (Where Web services are deployed     (have its own user accounts)
    so logged in user is already authenticated)          and have its own user accounts)
    The trust relationship configuration could solve the problem of authentication marked in second hop (2) by registering the IP address of PI server.
    Please help me understand how would it work to solve the first hop (1) problem and what needs to be done.
    Thanks,
    Parvinder

    Thanks Gaurav.
    The link talks about setting up the Trust with MDM server.
    The code sample provided there has the following step where user name is being set and passed to MDM:
    Use  command to authenticate user session on trusted connection
           TrustedUserSessionCommand  tuscTrustedUser =
           new TrustedUserSessionCommand(mySimpleConnection);
           //  Set the user name to use
           tuscTrustedUser.setUserName(UsernameAsString);
           tuscTrustedUser.setSession(session);
           tuscTrustedUser.execute();
           session =  tuscTrustedUser.getSession();
    I want to understand how to do that for MDM Web Services.
    I didn't see any method accepting this user name while calling the web service method / creating client object.
    So that link is still missing.
    Appreciate if anyone can help me with that.
    This is for MDM 7.1
    Thanks,
    Parvinder

  • Web Service -- ABAP

    Hello All
    I have created a Web Service with no authentication type.
    When I test the Web Service from the WS Navigator, system asks to enter the Logon again.
    Why is it so ?
    Is there some setting in Server that overrides my Web Service logon setting ?
    Or I am creating the Web Service incorrectly ?
    I have created this WS in Dev system( and collected the WDSL) and attached with the Transport Request.
    When this WS gets transported to the next system, WSDL has to be regenerated ?
    Please advice
    Cheers
    RJ

    Any one to help

  • Failed to test a SAP PI Published web service on SOAPUI

    Hi All,
    I have developed the RFC to Web service through SAP PI 7.1 . Web service published on 'Services Registry' and test on it. It accepts the my request and respond from SAP R3. All the message was successfully recorded on SXMB_MONI.
    In Integration Directory, i could view the web service URL . I navigated to the Sender Agreement -> Display WSDL and i could see the "WSDL URL' and wsdl content on large text box.
    I access the WSDL URL from SOAPUI tool and set the preference -> proxy setting also. it populated the request message successfully but respond gives the '400 Bad HTTP request' and Detail: -> illegal path specified  . No SOAPUI request recorded on SXMB_moni.
    i try the same following way also . i saved the WSDL on xml file and access it through the SOAPUI -> import project. that also failed on SOAPUI.
    Can you please help to solve the issue ?
    Thanks,
    Rehan

    Hi Rehan
    Please check the below blog, it might help
    Publish services from PI 7.1 to the Service Registry
    Consuming SAP PI published Web Service
    regards,
    Harish

  • Web service not visible in web service navigator

    Hi,
    Whenever i deploy my web service application ear, i am not been able to see the corresponding web service in web service navigator or in web service perspective. For any other project its working fine. but for this specific project its not at all working.
    I am not getting any warnings or errors while deploying. The deployment is successful. previously it was working  fine but now suddenly stopped working after doing some changes in entity bean. I tried recreating the web service and also tried changing the server. Also i deleted and recreated ear file. but no help.
    Any idea what exactly is wrong?

    Hi Abhijeet,
    I did got same error some time back. Go to visual Administrator and start the application if that does not work undeploy that application using Visual Administrator undeploy the deployed the Application, and then again deploy the application

  • How to delete the Webservice entry from Web service navigator?

    Hi,
    My current issue is that, developers have created many webserivces and these web services are visible in web service navigator that i access by following link
    http://<host>:<port>/wsnavigator
    But now we have to remove the unwanted webservices i.e. i want that unwanted webservices should not be visible to anyone when we access WSNAVIGATOR.
    How should i go about it?
    Am i required to undeploy the web services that is deployed from SDM GUI?
    Please pour in your valuable inputs.
    Any help would be highly appreciated.
    Regards,
    Ameya

    I had to revove the entry from VA. Removing this entry also removes the web service from ws navigator.

  • Regarding Web service navigator...

    HIII
    i have  issue that how can i check the location of Available web service in server. and How it can be deleted..
    Thanks

    hiii NAGA..
    I have to delete some web services from server  in this way that they r not visible in the web application navigator home page. I have found the ans of my last question regarding the " location of web apps" which is "usr\sap\e60\jc01\j2ee\cluster\server0\ apps\sap.com." at this location all the files r deployed . But I need a loaction where all the web services r found at single location.
    suppose i need the location of  "SLD START " service in that case the loaction will be usr-sap-e60-jc01-j2ee-cluster-server0- apps-sap.com-tcSLutil~wserver\server_js
    But now i search for CMSRTS the location will be different.
    I need a single location where all this files resides.
    how can i  deploy my web service to web service navigator . ???
    Thanks in advance...

  • Error while testing Web Service in WS Navigator

    Hello again,
    i'm trying to test the WSDL with WS Navigator from the Webservice ECC_PURCHASEREQUESTCRTRC created with ECC.
    It finds the WSDL, i can insert parameter but the result is this Error:
    Web-Service returned error. error code: "(http://schemas.xmlsoap.org/soap/envelope/)Server" error string: "Error during proxy processing"
    so what went wrong?

    The Log says that:
    Server Exception: Error during proxy processing; nested exception is:
    com.sap.engine.services.webservices.jaxrpc.exceptions.SOAPFaultException: Error during proxy processing
    [EXCEPTION]
    java.rmi.ServerException: Server Exception: Error during proxy processing; nested exception is:
    com.sap.engine.services.webservices.jaxrpc.exceptions.SOAPFaultException: Error during proxy processing
    at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.processFault(SOAPTransportBinding.java:1962)
    at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.call_SOAP(SOAPTransportBinding.java:1360)
    at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.call_SOAP_Idenpotency(SOAPTransportBinding.java:969)
    at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.callWOLogging(SOAPTransportBinding.java:950)
    at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.call(SOAPTransportBinding.java:907)
    at com.sap.engine.services.webservices.espbase.client.dynamic.impl.DInterfaceInvokerImpl.invokeOperation(DInterfaceInvokerImpl.java:76)
    at com.sap.esi.esp.wsnavigator.lib.Operation.execute(Operation.java:171)
    at com.sap.esi.esp.wsnavigator.WSNavigator.fireExecuteCurrentOperation(WSNavigator.java:600)
    at com.sap.esi.esp.wsnavigator.wdp.InternalWSNavigator.fireExecuteCurrentOperation(InternalWSNavigator.java:310)
    at com.sap.esi.esp.wsnavigator.ResultView.onPlugFromLogoView(ResultView.java:1219)
    at com.sap.esi.esp.wsnavigator.wdp.InternalResultView.wdInvokeEventHandler(InternalResultView.java:491)
    at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:142)
    at com.sap.tc.webdynpro.progmodel.window.ViewController.invokeInboundPlugHandler(ViewController.java:446)
    at com.sap.tc.webdynpro.clientserver.cal.NavigationManager.processInboundPlugQueue(NavigationManager.java:305)
    at com.sap.tc.webdynpro.clientserver.cal.NavigationManager.navigate(NavigationManager.java:320)
    at com.sap.tc.webdynpro.clientserver.phases.NavigationPhase.execute(NavigationPhase.java:63)
    at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequestPartly(WindowPhaseModel.java:162)
    at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doProcessRequest(WindowPhaseModel.java:110)
    at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:97)
    at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:514)
    at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:55)
    at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.doExecute(ClientApplication.java:1652)
    at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.doProcessing(ClientApplication.java:1466)
    at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doApplicationProcessingStandalone(ApplicationSession.java:884)
    at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doApplicationProcessing(ApplicationSession.java:856)
    at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:343)
    at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:315)
    at com.sap.tc.webdynpro.serverimpl.core.AbstractDispatcherServlet.doContent(AbstractDispatcherServlet.java:87)
    at com.sap.tc.webdynpro.serverimpl.wdc.DispatcherServlet.doContent(DispatcherServlet.java:76)
    at com.sap.tc.webdynpro.serverimpl.core.AbstractDispatcherServlet.doPost(AbstractDispatcherServlet.java:62)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
    at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:152)
    at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.doWork(RequestDispatcherImpl.java:359)
    at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:476)
    at com.sap.tc.webdynpro.serverimpl.wdc.ForwardServlet.doPost(ForwardServlet.java:63)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
    at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:152)
    at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:38)
    at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:400)
    at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:203)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:438)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:427)
    at com.sap.engine.services.servlets_jsp.filters.DSRWebContainerFilter.process(DSRWebContainerFilter.java:38)
    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    at com.sap.engine.services.servlets_jsp.filters.ServletSelector.process(ServletSelector.java:80)
    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:268)
    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    at com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:81)
    at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    at com.sap.engine.services.httpserver.filters.ResponseLogWriter.process(ResponseLogWriter.java:60)
    at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    at com.sap.engine.services.httpserver.filters.DefineHostFilter.process(DefineHostFilter.java:27)
    at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    at com.sap.engine.services.httpserver.filters.MonitoringFilter.process(MonitoringFilter.java:29)
    at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    at com.sap.engine.services.httpserver.filters.MemoryStatisticFilter.process(MemoryStatisticFilter.java:54)
    at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    at com.sap.engine.services.httpserver.filters.DSRHttpFilter.process(DSRHttpFilter.java:42)
    at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    at com.sap.engine.services.httpserver.server.Processor.chainedRequest(Processor.java:447)
    at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.process(Processor.java:264)
    at com.sap.engine.services.httpserver.server.rcm.RequestProcessorThread.run(RequestProcessorThread.java:56)
    at com.sap.engine.core.thread.execution.Executable.run(Executable.java:115)
    at com.sap.engine.core.thread.execution.Executable.run(Executable.java:96)
    at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:315)
    Caused by: com.sap.engine.services.webservices.jaxrpc.exceptions.SOAPFaultException: Error during proxy processing
    at com.sap.engine.services.webservices.espbase.client.bindings.impl.FaultUtil.buildFaultException_SOAP11(FaultUtil.java:220)
    at com.sap.engine.services.webservices.espbase.client.bindings.impl.FaultUtil.buildFaultException(FaultUtil.java:65)
    at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.processFault(SOAPTransportBinding.java:1924)
    ... 73 more
    Datum:     Single Click Filter by Datum     2011-01-18
    Zeit:     Single Click Filter by Zeit     09:39:05:734
    Kategorie:     Single Click Filter by Kategorie     com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding
    Ort:     Single Click Filter by Ort     com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding
    Applikation:     Single Click Filter by Applikation     sap.com/tcesiespwsnavui
    Thread:     Single Click Filter by Thread     Thread[HTTP Worker [@18923517],5,Dedicated_Application_Thread]
    Datenquelle:          j2ee\cluster\server0\log\defaultTrace_00.trc
    Argumente:          
    DSR-Transaktion:     Single Click Filter by DSR-Transaktion     41dd215022de11e08794000c2952e027

  • Error while executing Secure SOAP web service from Web Service Navigator

    Hi All,
    I have created a web service for a stateless session bean choosing option "Secure SOAP".
    When I am testing it through web service navigator, it is showing following error:-
    Security: Authentication expected but missing
    And in response text it is showing following :-
    HTTP/1.1 500 Internal Server Error
    Connection: close
    Server: SAP J2EE Engine/7.00
    Content-Type: text/xml; charset=UTF-8
    Date: Wed, 17 Dec 2008 05:42:10 GMT
    Set-Cookie: <value is hidden>
    <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>Security: Authentication expected but missing</faultstring><detail><ns1:com.sap.engine.interfaces.webservices.runtime.ProtocolException xmlns:ns1='http://sap-j2ee-engine/error'>Security: Authentication expected but missing</ns1:com.sap.engine.interfaces.webservices.runtime.ProtocolException></detail></SOAP-ENV:Fault></SOAP-ENV:Body></SOAP-ENV:Envelope>
    Can anybody help me with above thing?
    And my second question : I have created web service with "Basic Auth SOAP" option. and while executing at web service navigator, its asking for username & password.
    What role / right should be granted to this user so as to make him able to execute this web service? This user must be a UME user, correct?
    Pls help me in resolving this.
    Thanks and regards,
    Amey Mogare

    Hi Fazal,
    I have read the thread, but my questions are still unanswered.
    1. I know how to set username and password while using "Basic Auth SOAP" protocol. But my question in this case is what are the accesses user requires to be able to execute web service.
    2. And about Secure SOAP, why is above mentioned error is appearing?
    Thanks and regards,
    Amey Mogare

  • Error 403 while executing Web Service through Web Service Navigator

    Hello All,
    I am trying to execute "Create Sales Order" Web Service from WS Navigator. After filling all the input parameters and clicking on execute button, I get a error message
    Failed Invalid Response code (403)
    I know the execution is not reaching the back end proxy class. Any inputs on what could be causing this issue?
    Regards,
    Abhishek

    Hi Abhishek,
    Error code 403 means that the [access is forbidden.|http://en.wikipedia.org/wiki/HTTP_403]
    This means that the user access that is being used to access the Web Service / Backend Proxy does not have enough authorizations to perform the action.
    Check this user id, and its roles.
    Regards,
    Alka.

  • Error while configuring Web service Navigator

    Hi Every one,
    I installed the "NW Sneak preview" 640 with SP11. I created the a Web service for the Java Bean and deployed it. But i am not able to see the deployed Web service in the "Web service Navigator". When i tried to configure it, i am getting the following error
    <b>Error connecting to server "http://<localhost>:50000"
    (http://<localhost>:50000/inspection.wsdl)
    com.sap.engine.webservice.javarpc.exceptions.invalid response code.
    Invaild Response code (404) Not found.</b>
    When i am clicking the SQL Trace, UDDI client, and Web service Navigator of "http://localhost:50000/index.html" page i am getting a 404 error.
    Can any one tell me how to solve this problem?
    Thank you
    Bhaskar

    Hi Bhaskar,
    Slim edition has some apps deactivated. You can deploy them with Visual Admin in the deployment service.
    regards,
    Flavio Lazanha

Maybe you are looking for