Skip to Content
author's profile photo Former Member
Former Member

Web Service Client !!

I am pretty new to creating/using web service through Enterprise Portal !!

Environment :

Portal = 6.0.2.4.6.Enterprise_Portal_Service_Pack_2

JDK = 1.3.1

WAS = 6.20 (I think , how can I verify ??)

I have published a portal service as web service and I have created a standalone client through the wizard provided. When I run a test client to invoke the web service , I get the following error. The error is also logged in soap.log file on the server. The portal service is running properly since I have also created an iView which invokes the service and it is working. I can also see the web service in the soap administration page. Is there something I am missing on the server which I need to set up !!

Nov 16, 2004 4:53:26 PM # Client_Thread_38 Warning Unable to internalize message

javax.xml.soap.SOAPException: Unable to internalize message

at com.inqmy.lib.jaxm.soap.SOAPMessageImpl.<init>(SOAPMessageImpl.java:140)

at com.inqmy.lib.jaxm.soap.MessageFactoryImpl.createMessage(MessageFactoryImpl.java:40)

at com.sapportals.portal.prt.service.soap.SOAPConnection.processSOAPPost(SOAPConnection.java:238)

at com.sapportals.portal.prt.service.soap.SOAPConnection.handleRequest(SOAPConnection.java:186)

at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:532)

at java.security.AccessController.doPrivileged(Native Method)

at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:415)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)

at com.inqmy.services.servlets_jsp.server.InvokerServlet.service(InvokerServlet.java:126)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)

at com.inqmy.services.servlets_jsp.server.RunServlet.runSerlvet(RunServlet.java:149)

at com.inqmy.services.servlets_jsp.server.ServletsAndJspImpl.startServlet(ServletsAndJspImpl.java:832)

at com.inqmy.services.httpserver.server.RequestAnalizer.checkFilename(RequestAnalizer.java:666)

at com.inqmy.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:313)

at com.inqmy.services.httpserver.server.Response.handle(Response.java:173)

at com.inqmy.services.httpserver.server.HttpServerFrame.request(HttpServerFrame.java:1277)

at com.inqmy.core.service.context.container.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:36)

at com.inqmy.core.cluster.impl5.ParserRunner.run(ParserRunner.java:55)

at com.inqmy.core.thread.impl0.ActionObject.run(ActionObject.java:46)

at java.security.AccessController.doPrivileged(Native Method)

at com.inqmy.core.thread.impl0.SingleThread.run(SingleThread.java:148)

Thanks

Bhabesh Patel

Add a comment
10|10000 characters needed characters exceeded

Related questions

2 Answers

  • author's profile photo Former Member
    Former Member
    Posted on Nov 22, 2004 at 09:17 AM

    Hello,

    This problem is due when the soap request sent by your webservice client is empty or not well formed (XML).

    I advise to use a http listener to catch all soap request to the portal to understand where is the problem is the message.

    Best Regards,

    Fabrice

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Nov 22, 2004 at 07:01 PM

    Bhabesh,

    first the simple one:

    Your Web AS (more precisely your J2ee engine) is definitely 6.20, as EP6 SP2 uses this version. If you want a easy way to check it, just call your server's url without the trailing "/irj". This should give you the J2ee engine's start page.

    Regarding your web service. Are you using ordinary Eclipse plus portal plugins or NetWeaver Developer Studio? The latter one create web service clients that don't work on SP2.

    Next, could it be your test client generates invalid SOAP messages? I, for instance use XML Spy and the SOAP test tool included in NetWeaver developer studio for web service testing. Maybe you simply try a different tool.

    Regards,

    Dominik

    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member

      Bhabesh,

      the creation of standalone web service clients is not suppoerted by the portal eclipse plugins. You can only create web service clients that run on EP.

      But your main problem probably is, that you have created your portal web service by using NW Developer Studio, too. This only works for SAP EP of NW04 (i.e running on Web AS 6.40). So, re-build the web service using the portal plugins and re-reploy the par file.

      For testing (and solely for this) the web service, you can use NW developer studio which features a nice plugin for creating soap requests. Alternatively, I like XML spy very much for this.

      Regards,

      Dominik

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.