PI Consume Restful Webservices

Hi,
I have scenario in which PI needs to consume Restful webservices.
I am looking at HTTP receiver adapter in which I want to set appropreate action (POST, GET, PUT or DELETE) based on mapping.
For example I want to DELETE purcahse order TXU-19282. The http request that sends to Restful webservice looks like as follows.
DELETE /restfulwebservice-war/poservice/TXU-19282 HTTP/1.0
Connection: close
Content-Type: text/xml
Content-Length: 0
Pragma: no-cache
Now my question is how do I set set above information on HTTP receiver adapater. I looked at dynamic configuration and could find it useful.
Also I am interested in finding how do I set both heder and Payload via mapping?
Please let me know.
Thank you,
Balaji

I dont think, there is an option to mention (POST, GET, PUT or DELETE) in HTTP reciever adapter.
usually , it is with JDBC adapter.
Lets wait for someone to answer as well. am not much sure.
Also I am interested in finding how do I set both heder and Payload via mapping?
Usually, header can be filled with XSL mapping. payload can also be filled with XSL or else with simple graphical mapping.
-santosh.

Similar Messages

  • How to consume REST WebService using Axis2 in Adobe CQ5.5

    Hi All,
        How to consume REST WebService using Axis2 in Adobe CQ5.5 ?
    Please help me with this.Thanks very much for your help.
    Thanks & Regards,
    Kumar

    We had enough trouble getting the "osgi compliant" Axis2 library to run in OSGI without spooky failures that we ended up re-writing everything utilizng JAX-WS. JAX-WS is present in the underlying JDK, you just need to create an OSGI fragment bundle that exposes these classes from the JDK. So basically a bundle that just exports:
    com.sun.xml.ws,
                                    com.sun.xml.ws.addressing,
                                    com.sun.xml.ws.addressing.model,
                                    com.sun.xml.ws.addressing.v200408,
                                    com.sun.xml.ws.api,
                                    com.sun.xml.ws.api.addressing,
                                    com.sun.xml.ws.api.client,
                                    com.sun.xml.ws.api.fastinfoset,
                                    com.sun.xml.ws.api.handler,
                                    com.sun.xml.ws.api.message,
                                    com.sun.xml.ws.api.message.stream,
                                    com.sun.xml.ws.api.model,
                                    com.sun.xml.ws.api.model.soap,
                                    com.sun.xml.ws.api.model.wsdl,
                                    com.sun.xml.ws.api.pipe,
                                    com.sun.xml.ws.api.pipe.helper,
                                    com.sun.xml.ws.api.server,
                                    com.sun.xml.ws.api.streaming,
                                    com.sun.xml.ws.api.wsdl.parser,
                                    com.sun.xml.ws.api.wsdl.writer,
                                    com.sun.xml.ws.binding,
                                    com.sun.xml.ws.client,
                                    com.sun.xml.ws.client.dispatch,
                                    com.sun.xml.ws.client.sei,
                                    com.sun.xml.ws.developer,
                                    com.sun.xml.ws.developer.servlet,
                                    com.sun.xml.ws.encoding,
                                    com.sun.xml.ws.encoding.fastinfoset,
                                    com.sun.xml.ws.encoding.soap,
                                    com.sun.xml.ws.encoding.soap.streaming,
                                    com.sun.xml.ws.encoding.xml,
                                    com.sun.xml.ws.fault,
                                    com.sun.xml.ws.handler,
                                    com.sun.xml.ws.message,
                                    com.sun.xml.ws.message.jaxb,
                                    com.sun.xml.ws.message.saaj,
                                    com.sun.xml.ws.message.source,
                                    com.sun.xml.ws.message.stream,
                                    com.sun.xml.ws.model,
                                    com.sun.xml.ws.model.soap,
                                    com.sun.xml.ws.model.wsdl,
                                    com.sun.xml.ws.org.objectweb.asm,
                                    com.sun.xml.ws.protocol.soap,
                                    com.sun.xml.ws.protocol.xml,
                                    com.sun.xml.ws.resources,
                                    com.sun.xml.ws.server,
                                    com.sun.xml.ws.server.provider,
                                    com.sun.xml.ws.server.sei,
                                    com.sun.xml.ws.server.servlet,
                                    com.sun.xml.ws.spi,
                                    com.sun.xml.ws.streaming,
                                    com.sun.xml.ws.transport,
                                    com.sun.xml.ws.transport.http,
                                    com.sun.xml.ws.transport.http.client,
                                    com.sun.xml.ws.transport.http.server,
                                    com.sun.xml.ws.transport.http.servlet,
                                    com.sun.xml.ws.util,
                                    com.sun.xml.ws.util.exception,
                                    com.sun.xml.ws.util.localization,
                                    com.sun.xml.ws.util.pipe,
                                    com.sun.xml.ws.util.xml,
                                    com.sun.xml.ws.wsdl.parser,
                                    com.sun.xml.ws.wsdl.writer,
                                    com.sun.xml.ws.wsdl.writer.document,
                                    com.sun.xml.ws.wsdl.writer.document.http,
                                    com.sun.xml.ws.wsdl.writer.document.soap,
                                    com.sun.xml.ws.wsdl.writer.document.soap12,
                                    com.sun.xml.ws.wsdl.writer.document.xsd,
                                    com.sun.xml.internal.bind,
                                    com.sun.xml.internal.bind.v2,
                                    com.sun.xml.internal.ws,
                                    com.sun.xml.internal.ws.addressing,
                                    com.sun.xml.internal.ws.addressing.model,
                                    com.sun.xml.internal.ws.addressing.v200408,
                                    com.sun.xml.internal.ws.api,
                                    com.sun.xml.internal.ws.api.addressing,
                                    com.sun.xml.internal.ws.api.client,
                                    com.sun.xml.internal.ws.api.fastinfoset,
                                    com.sun.xml.internal.ws.api.handler,
                                    com.sun.xml.internal.ws.api.message,
                                    com.sun.xml.internal.ws.api.message.stream,
                                    com.sun.xml.internal.ws.api.model,
                                    com.sun.xml.internal.ws.api.model.soap,
                                    com.sun.xml.internal.ws.api.model.wsdl,
                                    com.sun.xml.internal.ws.api.pipe,
                                    com.sun.xml.internal.ws.api.pipe.helper,
                                    com.sun.xml.internal.ws.api.server,
                                    com.sun.xml.internal.ws.api.streaming,
                                    com.sun.xml.internal.ws.api.wsdl.parser,
                                    com.sun.xml.internal.ws.api.wsdl.writer,
                                    com.sun.xml.internal.ws.binding,
                                    com.sun.xml.internal.ws.client,
                                    com.sun.xml.internal.ws.client.dispatch,
                                    com.sun.xml.internal.ws.client.sei,
                                    com.sun.xml.internal.ws.developer,
                                    com.sun.xml.internal.ws.encoding,
                                    com.sun.xml.internal.ws.encoding.fastinfoset,
                                    com.sun.xml.internal.ws.encoding.soap,
                                    com.sun.xml.internal.ws.encoding.soap.streaming,
                                    com.sun.xml.internal.ws.encoding.xml,
                                    com.sun.xml.internal.ws.fault,
                                    com.sun.xml.internal.ws.handler,
                                    com.sun.xml.internal.ws.message,
                                    com.sun.xml.internal.ws.message.jaxb,
                                    com.sun.xml.internal.ws.message.saaj,
                                    com.sun.xml.internal.ws.message.source,
                                    com.sun.xml.internal.ws.message.stream,
                                    com.sun.xml.internal.ws.model,
                                    com.sun.xml.internal.ws.model.soap,
                                    com.sun.xml.internal.ws.model.wsdl,
                                    com.sun.xml.internal.ws.org.objectweb.asm,
                                    com.sun.xml.internal.ws.protocol.soap,
                                    com.sun.xml.internal.ws.protocol.xml,
                                    com.sun.xml.internal.ws.resources,
                                    com.sun.xml.internal.ws.server,
                                    com.sun.xml.internal.ws.server.provider,
                                    com.sun.xml.internal.ws.server.sei,
                                    com.sun.xml.internal.ws.spi,
                                    com.sun.xml.internal.ws.streaming,
                                    com.sun.xml.internal.ws.transport,
                                    com.sun.xml.internal.ws.transport.http,
                                    com.sun.xml.internal.ws.transport.http.client,
                                    com.sun.xml.internal.ws.transport.http.server,
                                    com.sun.xml.internal.ws.util,
                                    com.sun.xml.internal.ws.util.exception,
                                    com.sun.xml.internal.ws.util.localization,
                                    com.sun.xml.internal.ws.util.pipe,
                                    com.sun.xml.internal.ws.util.xml,
                                    com.sun.xml.internal.ws.wsdl.parser,
                                    com.sun.xml.internal.ws.wsdl.writer,
                                    com.sun.xml.internal.ws.wsdl.writer.document,
                                    com.sun.xml.internal.ws.wsdl.writer.document.http,
                                    com.sun.xml.internal.ws.wsdl.writer.document,
                                    com.sun.xml.internal.ws.wsdl.writer.document.soap,
                                    com.sun.xml.internal.ws.wsdl.writer.document.soap12,
                                    com.sun.xml.internal.ws.wsdl.writer.document.xsd,
                                    com.sun.xml.internal.messaging.saaj.soap

  • How to expose a bapi as Rest webservice to consume in web applications

    Hello experts , i now seriously need your suggestion here. Is there a way to expose a BAPI as a rest webservice which can be consumed by a web application in the end.
    What is ICF ( Internet Communication Framework) ? Does this help in generating web service from BAPI ?
    Netweaver Gateway might help to generate services but may not be recommended here in our scenario.

    Please refer Real Web Services with REST and ICF for creation of rest services in sap. The BAPI will have to be called in your handler class.
    I think your best bet would be to transfer the data in the body of the http request and use simple transformation(with multiple roots) to convert the xml data to sap formats. GZIP can also be used to compress the data that is being sent. We have done this successfully in one of our projects.
    However this approach(RESTful Service) would involve more work when compared to the approach suggested by Vikram. If SOAP based services are ok, then you should go ahead with Vikram's approach.

  • Consume a restful webservice using plsql

    Hi
    We need to consume a restful webservice and this needs to be implemented using plsql.
    I know that we can use utl_dbws or utl_http to consume SOAP based web services but
    there is not much information on how to consume restful web services.
    kindly let me know if you have information.
    Cheers
    rigel

    851866 wrote:
    Im looking for the opposite scenario where i need to access a restful web service from plsql.Why would a RESTful call be any different from a normal URL call? HTTP is the transport mechanism - and UTL_HTTP is used in PL/SQL as the client side of a HTTP conversation.
    I posted sample code of a how to use PL/SQL as a brower client in {message:id=1925297} - using a pipeline table to demonstrate the contents returned by the web server in response using plain SQL.
    Depending on what the contents is, you can write it into a BLOB (dealing with binary data returned), a CLOB (for XML data for example), or using varchar2 you can for example parse a text/csv response (no need for a pipeline in such a case).
    The only real issue I can see with a RESTful service is URL construction - as the URL becomes "parameterised" and not just the query string itself, or the data contents (name values) in the POST structure.

  • Need to consume Beehive webservices but can't figure out the best way

    Hi
    I'm completely new to the Beehive scene and I've been commissioned to write a sample application that consumes Beehive Webservices, just add a File to a certain workspace and be able to authenticate users via SSO and basic Authentication to a local DB. Initially I was told that Beehive had only support for REST webservices, so I thought it might be just easier to just go with REST, do a simple POST/GET request and get results, however I'm having a hard time running the sample code as a class is missing.
    However I just found that Beehive also has support for SOAP webservices (I somehow like them more as I'm more used to them) but same problem, I don't know how would I authenticate, I found were the WDSL are stored and everything but I just don't understand how would I make a user authenticate with SSO or any other method
    Finalyl there's this BPEL workflow for jDeveloper and JCR API.
    I just don't know where or how to start, tutorials are oracle.com assume too many things, I was thinking in creating proxy classes using the Beehive WSDL's and consume the services this way, however I still don't understand how to authenticate.
    Can anyone give me directions on this? How to use Beehive's SSO and Basic Authentication? thanks in advance

    Hi,
    Regarding the basic http authentication, an answer was provided in your other post:
    Authentication with SOAP API
    And regarding the missing class in the Rest sample code. I'm currently taking a look at it and, hopefully, I will get you an update on this in the following post:
    Failure Class not bundled with BDK Samples
    Regards,
    Ward

  • Url service data control - problem while  POSTing to a restful webservice

    Hi,
    I am trying to call a restful webservice to add a new employee .I have created the url service data control. The service method consumes XML.
    When i am creating the url service datacontrol I selected the http method as POST and giving the servicepath and servicename as the source. After providing the xsd's path and all , when I test the url connection, I am getting the following error message:
    URL Test: Received Error: Method Not Allowed
    This might be because the clicking of the test url button is sending the get request, but the actual method is POST.
    Now under the data controls navigator, If i view the newly created data control, i could see the loadData(Object) method which i assume is for retrieving the data from the service. But since i have mentioned the method as POST, why such a method is created? Also if its there, can I use the same for insert and update? I have used this loadData (Object) method to create a button which calls the webservice upon click. Under the data control property inspector, i changed the supportsupdate attribute's value to true. But when i am trying to save the employee from the jspx page, I am getting the following message in the integrated weblogic's log
    Couldn't get access to the data source. Cause Unsupported Media Type exception in rest service
    And on the server side I am getting the following error message:
    No message body reader has been found for request class Employee, ContentType application/octet-stream.
    I think the request is not going as XML. But while creating the datacontrol i have specified the xsd document for the iput xml request. Does ADF automatically creates the XML from the input parametres? If it does not, then what could be done to achieve that? The default actionListener of the submit button is #{bindings.loadData.execute}. Do i have to override it to send the XML request? Or have I missed anything in trying to achieve what i intend?
    I had refered this link for reference :
    http://docs.oracle.com/cd/E18941_01/tutorials/jdtut_11r2_53/jdtut_11r2_53.html
    Rampal
    Edited by: user12011868 on Jan 22, 2012 10:03 PM

    Hi Frank,
    I had specified the HTTP method as POST as well as PUT. But the same error is appearing in the both the cases.
    URL Test: Received Error: Method Not Allowed
    And when I am clicking on the 'Test URL Connection' , I can't see any option of selecting the HTTP method. This option only appears in the step 2 of creating the URL service data control where we mention the URL endpoint and the source.
    What could be the reason for the error.
    Rampal

  • Consuming RESTful webservive in SAP PI 7.3.1

    Dear all,
    I am trying to implement a scenario to consume a synchronous RESTful webservice in PI following the blog
    Consuming Synchronous RESTful Web Service with PI - I As mentioned in the blog, i have taken actual request message type structure at source end and dummy message type with a single node as target message in request mapping. However i am not clear with the design objects in ESR. Could anyone throw lights on this.
    Thanks in advance.
    Regards
    Koti Reddy

    Hi Koti,
    In the blog, it says that the ESR objects are used to dynamically set the URL. The HTTP method used is GET and it gets its input from the source message so yes, dynamic configuration should be used.
    Regards,
    Mark

  • How to set username and password before redirecting to a RESTful webservice

    I am a .Net developer who has developed a webservice used by my ColdFusion colleagues. They are using ColdFusion 9 but I'm not sure if they have incorporated any of the newer features of ColdFusion in their apps. Here is a snippet of how they have been invoking the webmethods:
    <cfscript>
                         ws = CreateObject("webservice", "#qTrim.webServiceName#");
                         ws.setUsername("#qTrim.trimAcct#");
                         ws.setPassword("#qTrim.trimpwd#");
                         wsString=ws.UploadFileCF("#qTrim.webserviceurl#","#objBinaryData#", "#qFiles.Filename#", "Document", "#MetaData#");
                </cfscript>
    As I understand things, the .setUsername and .setPassword correspond to the Windows credentials the CF Admin set when the URL of the .Net webservice was "registered" and given its "name" (for the CreateObject statement above). I have 4 webmethods that are all invoked in this manner and this SOAP protocol works adequately for us. Please note that this ColdFusion web app authenticates anonymous remote internet users by prompting for a username and password and compares them to an application database (i.e. Microsoft calls this "forms authentication"). Because only a few Windows domain accounts are authorized to call this .Net webservice, the above code always uses the same username/password constants and it all works.
    My question involves the newest webmethod added to the .Net webservice. It requires that callers must invoke it as a RESTful service which means it must be invoked by its URL. Here is a snippet of C# code that invokes it from an ASP.NET webclient:
                string r = txtRecordNumber.Text;
                string baseurl = "http://localhost/sdkTrimFileServiceASMX/FileService.asmx/DownloadFileCF?";
                StringBuilder url = new StringBuilder(baseurl);
                url.Append("trimURL="); url.Append(txtFakeURLParm.Text);
                url.Append("&");
                url.Append("TrimRecordNumber="); url.Append(txtRecordNumber.Text);
                Response.Redirect(url.ToString());
    I assume a ColdFusion script could easily build a full URL as above with appended querystring parameters and redirect. Is there some way for the CF code redirecting to a RESTful webservice (by way of its URL) to set the Username and Password to this Windows account mentioned above? When the DownloadFileCF webmethod is hit it must be with the credentials of this special Windows domain account. Can that be set by ColdFusion someway to mimic the result of the SOAP technique (the first snippet above).
    I hope my question is clear and someone can help me make suggestions to my ColdFusion colleagues. Thanks.

    Can you clarify what you mean by "establish a different Windows identity"?  Usually passing identity to a web site or service means adding something to the request's HTTP headers.  This could be a cookie in the case of .NET forms authentication or the "Authorization" header in the case of basic authentication.
    The SOAP web service invocation code you posted does use basic authentication, according to the CF docs "ColdFusion inserts the user name/password string in the authorization request header as a base64 binary encoded string, with a colon separating the user name and password. This method of passing the user name/password is compatible with the HTTP basic authentication mechanism used by web servers."
    http://help.adobe.com/en_US/ColdFusion/9.0/Developing/WSc3ff6d0ea77859461172e0811cbec13a13 -7fe0.html
    If you need to mimic the SOAP techinque you should have basic authentication enabled for your REST service endpoints.
    If your authentication method is different then CF developers will need to add the appropriate HTTP headers to their service calls.  Note that calling a REST service from CF would probably be accomplished using the CFHTTP tag if the service is designed to be consumed by the CF server.

  • Brief explaination of REST,Webservices,CSON and JSON

    brief explaination of REST,Webservices,CSON and JSON

    http://www.simplecodestuffs.com/what-is-the-difference-between-http-and-rest-and-soap-in-web-services/
    SOAP uses WSDL for communication between consumer and provider, whereas REST just uses XML or JSON to send and receive data
    WSDL Defines contract between client and service and is static by its nature. In case of REST contract is somewhat complicated and is defined by HTTP, URI, Media Formats and Application Specific Coordination
    Protocol. It’s highly dynamic unlike WSDL.
    SOAP doesn’t return human readable result, while REST result is readable with is just plain XML or JSON
    This is not true. Plain XML or JSON are not RESTful at all. None of them define any controls(i.e. links and link relations, method information, encoding information etc…) which is against REST as far as messages must be self contained and coordinate interaction
    between agent/client and service.
    With links + semantic link relations clients should be able to determine what is next interaction step and follow these links and continue communication with service.
    It is not necessary that messages be human readable, it’s possible to use cryptic format and build perfectly valid REST applications. It doesn’t matter whether message is human readable or not.
    Thus, plain XML(application/xml) or JSON(application/json) are not sufficient formats for building REST applications. It’s always reasonable to use subset of these generic media types which have strong semantic meaning and offer enough control information(links
    etc…) to coordinate interactions between client and server.
    REST is over only HTTP. HTTP is most widely used and when we talk about REST web services we just assume HTTP. HTTP defines interface with it’s methods(GET, POST, PUT, DELETE, PATCH etc) and various headers
    which can be used uniformly for interacting with resources. This uniformity can be achieved with other protocols as well.
    REST permits many different data formats where as SOAP only permits XML.
    While this may seem like it adds complexity to REST because you need to handle multiple formats, in my experience it has actually been quite beneficial. JSON usually is a better fit for data and parses much faster. REST allows better support for browser clients
    due to it’€™s support for JSON.
    If this helped you resolve your issue, please mark it Answered

  • Getting OutOfMemoryError with REST webservice

    Hi,
    I need some help with my configuration regarding
    the listener (version 2.0.1.64.14.25 as stand alone with Application Express 4.2.1.00.08):
    I consume (via $.ajax(...)) a REST-Webservice for request a clob value.
    Configuration of my Ressource Handler:
    method: GET
    Requires Secure Access: No
    source type: "Query one Row"
    Pagination Size: 1
    Source: select id, col3 from csvloader where id = :ID
    This works as excepted until I want to load a value that is bigger then 65 kb.
    In my cmd box, where the listener is stated, I noticed the following error:
    22.03.2013 14:18:49 oracle.dbtools.rt.web.WebErrorResponse internalError
    SCHWERWIEGEND: Java heap space
    java.lang.OutOfMemoryError: Java heap space
    ("SCHWERWIEGEND" means "fatal" in german)
    In order to avoid this error, I tried to increase the heap space:
    java -Xms500m -Xmx1024m -jar apex.war
    -> no change, still getting OutOfMemoryError (HTTP 500 Errorcode)
    Any suggestions, hints?
    Thanks for your help!
    Michael

    Hi!
    I'm still working on this topic. I updated the listener to the newest version 2.0.2.133.14.47
    but this is not a solution for my problem.
    Steps I've done:
    - raised JVM-Memory: GlassFish -> JVM configuration -> JVM options: add/set "-Xmx1024m" and "-XX:MaxPermSize=256m"
    - raise "-Xmx1024m" to "-Xmx1224m" -> glassfish doesn-'t start
    Maybe I have a problem with my os: I use windows XP (32bit) in a virtual machine. Seems that JVM don't get enough
    memory. On the other hand, I just want to get about 65 - 72,5 KB from a blob-field to my browser....
    Any suggestions for me?
    Thanks a lot!
    Michael

  • Connection issue while accessing a jersey restful webservice using aysynch callback method.

    Hi,
    I am having one consumer and producer application. Producer is a Jersey restful webservice deployed in a tomcat server. Consumer side I am using executor service to create one scheduler which will keep on polling and creates a new Thread where I am making a asynch callback req to the service(Producer). But the problem is after my asynch executor thread will die still I can see one connection in deployed server.
    I used yourkit profiler, I can see one thread in runnable state even when the asynch executor dies.
    I think bec of scheduler still there is a connection between client and service. I wanted to create multiple consumer to process multiple thread but because of thread leakage I am not able to proceed.
    Could you please help me on this?

    Err, close the connection?

  • Consuming a webservice in ABAP ECC 6.0 without using XI/ PI

    Hi Experts,
    I wanted to consume an external webservice without using XI / PI.After doing my homework and search on sdn I came to know that we can consume webservices in ABAP using proxies using SE80(Enterprise Services).
    I am trying to create a client proxy with the URL of webservice.It asks me the option to choose between URL or HTTP.
    I am selecting URL and in the second screen it asks about the package details and after that it finishes.Later I get an error message stating "NO VENDOR SPECIFIED".Its not allowing me to create a proxy.
    So, here are my questions.
    Does anyone faced the same kind of problem?
    Can we really consume a webservice without using XI / PI or any other middleware?
    Is it possible to consume the webservice only with URL or WSDL file ?
    Please let me know the exact process.
    Thanks in Advance.
    Shanker Pandey.

    Hi Martin,
      Please check these following links. Though you have reported already, these may help
    Proxy Object generation error using Wizard for Web Service Consumption
    Also, please have a look @ /people/thomas.jung/blog/2006/03/13/develop-a-web-service-that-sends-an-email--in-abap-netweaver-04s
    Hope this helps,
    Karthik

  • Getting error while consuming google webservice in jspDynpage

    Hi All,
    I am consuming google webservices in my JspDyn page
    i am getting following error
    An exception occurred while processing a request for :
    iView : GoogleSer.google
    Component Name : GoogleSer.google
    Could not find portal application <b>com.company.global.enterprise.portal.wsdl.webservices.service.</b>
    Please help me to resolve this issue
    code ::
    MyGoogle googleService =
    (MyGoogle) PortalRuntime.getRuntimeResources().getService("com.company.global.enterprise.portal.wsdl.webservices.service.MyGoogle");
    GoogleSearchResult result = googleService.doGoogleSearch("google", "SAP", 0, 10, false, "", false, "", "", "");
    Thanks & Regards
    Rudra

    Hi,
    I am still having the same problem, however the scenario in which I am getting varies.
    I am getting this exception:
    "com.sap.engine.services.webservices.jaxm.soap.accessor.NestedSOAPException: IOError while working with the message."
    Some users when trying to login into the portal are getting blank screen and for some the portal launcher page is loading fine and could go to the Home Page.
    When I view the logs I am seeing the Nested Soap Exception.
    Any Ideas??? Starting the J2EE engine also did'nt help.
    Thanks in advance.
    Madhavi

  • Error While Consuming the webservice in ABAP

    Hi,
      I am trying to consume a webservice in ECC. I have imported the WSDL and generated the proxy. Did the configuration in the SOAMANAGER. While calling the webservice from the program I am getting the following error message. "SRT: Unsupported xstream found: ("HTTP Code 400  : Bad Request")"
       Any help is appreciated.
    Thanks
    Raghavendra Kuamr

    Hi,
    Check ST11 to find detailed log of issue, most likely you are passing "WS-A" message id along with request (check settings in SOAMANAGER Logical Port).
    Try calling service after suppressing "Message Id transfer". See SAP Note: 1361688 and related notes in 0001292171
    Regards,
    Gourav
    PS: please search forum before posting questions.

  • While Consuming a WebService in JSP Dyn Page - There is an Error

    Hi Friends,
    I have a web service created in ASP.NET web Service.
    And I have Consumed the Web Service using WSDL URL.
    I need to write a code to refer that class in the JSP DynPage
    I have created like this in DoIntialization
    MyServiceName obj=(MyServiceName) PortalRuntime.getRuntimeResources().getService(MyServiceName.KEY);
    int a = 10;
    int b = 20;
    obj.Add1(a,b);
    but it shows an error
    "The method Add1 Method(Add1 Method) is the type. MySErviceName is not Applicable for the arguements(int,int)"
    Please Help me in this regard.
    Thanks in Advance
    Thanks & Regards,
    Palani

    Hi Andy,
    I will let u know the sequence which i followed to consume the Webservice.
    NWDS --> File --> New --> Project --> Portal Application --> Create New Portal App Project.
    The Project is created.....
    After that i want to consume the Webservice for the same project...
    for that...
    NWDS --> File --> New --> Other --> Portal Application --> Create New Portal Application Object --> Selecting My Project?(intended prjct) --> Portal Webservice --> Portal Service from WSDL file - Client Side --> My WSDL URL --> Selecting the methods which i need to expose from the Webservice --> I gave unique name for my 1) Service 2) Alias 3) Package....and that was done....(other way is to add from portalapp.xml ??)
    After that i created a new JSPDyn page for my application in DoInitialization() method i tried to access the method from that webservice using the following code...
    MyServiceName obj=(MyServiceName) PortalRuntime.getRuntimeResources().getService(MyServiceName.KEY);
    I am successfully able to access the method from the webservice using the object which i have created but i am not able to pass arguments to that method...???
    I tried consuming same webservice created in .NET in .NET itself and i am able to pass arguments successfully.
    I tried to consume webservice created in ABAP in .NET and able to implement successfully...
    but the same ABAP webservice when  i tried to consume its not working with this NWDS.
    Is there any thing else i need to follow while consuming a webservice in the EP Perspectice of NWDS ???
    Deployable Proxy is required for that ?? if required how to create and use that ??
    Thanks in Advance,
    Palani

Maybe you are looking for

  • Subcontracting Error at GRN

    Dear Expert, I am doing a Subcontracting scenario. At the time of GRN an error throws " Account xxxxxxx requires an assignment to a CO object" The GL is subcontracting expense GL. I have searched every where all are saying to maintain the GL in OKB9

  • How to dowload a file to a cd?

    How do I download a file to a cd?

  • Asha 305 Whats app problem

    Asha 305 v7.42 whatsapp problem SDRAHEEM

  • Can't install itunes 5.01 or 6 either

    using G4 450 with os X 10.3.9. every itunes upgrade worked until 5.01. currently running itunes 5.

  • How to validate empty Text Field?

    Hi, I am Thirupathi, I am new to JSF. I am able to validate the value of a component which has some value using attribute validator="#{UserNumberBean.validate}" in this case it is calling validate method of UserNumberBean. but if i keep the field emp