Servlet as a client to the web-service

Hi all, I am new to this field of developing web services.
I have designed a simple web service, that provides some lookup and search operation. I have developed the web service using JWSDP 1.5.0, Tomcat 5.0 and jdk1.5.0_03. I have also developed client applications using the wscomp and ant tools and they are working fine. The applications talk to the web service after I type in the command ant run-client on the command prompt.
Now, I have to develop a servlet which will be the clients to the web service. How do I do that?

By reading a tutorial about servlets maybe?

Similar Messages

Web-service client for legacy web service

I currently access a legacy server (Lotus Domino 7) via CORBA. I thought a web service (my second) would be faster, but a whole day's research has uncovered only obsolete or trivial examples.
The WSDL generated by the server is rpc/encoded so wsimport cannot generate the necessary "artifacts" for a web service client.
The web service is simple: it accepts two java.lang.Strings, and returns a java.lang.String of XML. The "dynamic proxy" approach from 1.4.2 seems to have disappeared; I was hoping that approach would let me just hand-code a single "artifact" - an SEI based on the method information in the WSDL.
1) What classes in JAX-WS will let my web service client communicate with rpc?
2) With such a simple signature, do I need any other "artifacts" beyond an SEI?
Thanks for any help!

In case anyone's search leads them here, I've posted the solution at:
*[http://www.pby.com/general.nsf/webarticles/dominowebservice01]*
It is an exhaustive article (not "Hello World"!) that goes through several versions of the web service and client - hopefully explaining all* pieces of the puzzle:
~ web service code,
~ WSDLs
~ schema
~ thoroughly-documented clients that do and do not use JAXB
~ ... that use generated artifacts
~ ... that customize existing POJOs
~ the SOAP messages generated in each direction
~ the necessary JAXB annotations
~ explanations of how the code works
~ explanations of how namespaces affect the code
~ on and on and on...
My constant goal was to write an uncomplicated solution that uses as few artifacts (two) and annotations as possible. The end result is a small, fast JAX-WS 2.0 client that uses JAXB to invoke and consume a secured Domino 7 (1.4.2 JVM + AXIS) web service, using RPC/literal SOAP messages.

Error when running the Web Services java client file

Hi,
I am working on web services with 9iAS.
I am using the StatelessExample file included during installation.
The ear file was created and the application was deployed using OEM Web.
But when I try to execute the client java file StatelessClient. I get an error. The error is something about content type.
The error message is pasted below.
And also how do I run the web service on the browser.
Please help.
regards
Kamlesh
D:\ora9ias_portal\j2ee\home\demo\web_services\java_services\client>java -classpa
th .;StatelessExample_proxy.jar;%CLASSPATH%; StatelessClient
Exception in thread "main" [SOAPException: faultCode=SOAP-ENV:Protocol; msg=Unsu
pported response content type "text/html", must be: "text/xml&quo
t;. Response was:
<HTML><HEAD><TITLE>500 Internal Server Error</TITLE><
/HEAD><BODY><H1>500 Internal Server Error</H1><PRE>or
acle.j2ee.xanadu.JasperGenerationError: no source generated during code generati
on!: 1 in getFile name: oracle\j2ee\ws_example\StatelessExample.class
 1 in getFile name: oracle\j2ee\ws_example\StatelessExample.java
 error: error message 'class.format' not found binar
y class definition not found: oracle.j2ee.ws_example.StatelessExample
 
 at oracle.j2ee.ws.JavaWrapperGenerator.generate(JavaWrapperGener
ator.java:267)
 at oracle.j2ee.ws.RpcWebService.generateWrapperClass(RpcWebServi
ce.java:662)
 at oracle.j2ee.ws.RpcWebService.generate(RpcWebService.java:436)
 at oracle.j2ee.ws.RpcWebService.getWrapper(RpcWebService.java:76
7)
 at oracle.j2ee.ws.RpcWebService.doPost(RpcWebService.java:309)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:283)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:336)
 at com.evermind[Oracle9iAS (9.0.2.0.0) Containers for J2EE].serv
er.http.ResourceFilterChain.doFilter(ResourceFilterChain.java:59)
 at oracle.security.jazn.oc4j.JAZNFilter.doFilter(JAZNFilter.java
:283)
 at com.evermind[Oracle9iAS (9.0.2.0.0) Containers for J2EE].serv
er.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:523)
 at com.evermind[Oracle9iAS (9.0.2.0.0) Containers for J2EE].serv
er.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:2
69)
 at com.evermind[Oracle9iAS (9.0.2.0.0) Containers for J2EE].serv
er.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:735)
 at com.evermind[Oracle9iAS (9.0.2.0.0) Containers for J2EE].serv
er.http.AJPRequestHandler.run(AJPRequestHandler.java:151)
 at com.evermind[Oracle9iAS (9.0.2.0.0) Containers for J2EE].util
.ThreadPoolThread.run(ThreadPoolThread.java:64)
 </PRE></BODY></HTML>
at org.apache.soap.rpc.Call.getEnvelopeString(Call.java:201)
at org.apache.soap.rpc.Call.invoke(Call.java:260)
at oracle.j2ee.ws_example.proxy.StatelessExampleProxy.makeSOAPCallRPC(St
atelessExampleProxy.java:51)
at oracle.j2ee.ws_example.proxy.StatelessExampleProxy.helloWorld(Statele
ssExampleProxy.java:35)
at StatelessClient.main(StatelessClient.java:8)

If you are getting this error, then you are most likely compiling your code with a different JVM than what is shipped with the application server. Oracle9iAS Release 2 (9.0.2) uses the JDK1.3.1. I got this error when I compiled the code with JDK1.4.0_01.

How to Authenticate the Web Service from my Java Client?

Hi All,
I am a newbie. I am working in Microsoft Technology. But due to a critical requirement, I am suppose to write a Java Web Service Client application. I some how managed to create the Client Application. The application works fine if the Authentication is turned off in the web service level itself. I am unable to or unaware of authentication in Java World. I have written a .NET Client application where I am able to set the Credentials but in Java world no property or method allows me to set it.
Anybody knows how to solve this problem?
My configuration is,
JDK - JDK 1.5.0.16
IDE - Netbeans 6.1
Web Server - Tomcat 6.0
SOAP - Native C++ SOAP
How do I did?
- Created a Java Web Service Client Application.
- Added the Web Reference to the SOAP WSDL url.
- Initialized the class object using the WSDL generated SOAP classes (Reference classes)
My code look like,
String result = "";
 try {
 QName name = new QName("http://eaglesuite20/eaglesoap.wsdl", "eaglesoap");
 eaglesuite20.eaglesoap.Eaglesoap service = new eaglesuite20.eaglesoap.Eaglesoap(new URL("http://phobos:1011/?wsdl"), name);
 eaglesuite20.eaglesoap.EaglesoapPortType port = service.getEaglesoap();
 // TODO initialize WS operation arguments here
 eagle.Request submitRequest = new eagle.Request();
 submitRequest.setRequestType(eagle.RequestType.E_B_SCHEDULE_DEF);
 submitRequest.setOperation(eagle.Operation.READ);
 eagle.FilterDefinition filter = new eagle.FilterDefinition();
 filter.setField(new JAXBElement<String>(new QName("urn:eagle", "Field"), String.class, "SHOW_SCHEDULED"));
 filter.setValue(new JAXBElement<String>(new QName("urn:eagle", "Value"), String.class, "SHOW_SCHEDULED"));
 filter.setOperator(eagle.EOperators.EQUAL);
 eagle.FilterDefinitions filDefs = new eagle.FilterDefinitions();
 filDefs.getFilterDefinition().add(filter);
 submitRequest.setFilterDefinitions(new JAXBElement<eagle.FilterDefinitions>(new QName("urn:eagle", "FilterDefinitions"), eagle.FilterDefinitions.class, filDefs));
 // TODO process result here
 result = port.submitData(submitRequest);
 //out.println("Result = " + result);
 } catch (Exception ex) {
 // TODO handle custom exceptions here
 out.println(ex.getMessage());
 }Thanks in Advance.

Hi
Did you get your problem solved? Can you please help as I am getting null pointer exception when I invoke a call to web service which is secured/
Please help!!!!!!!!! this is urgent.

How to change the web service address of NetBeans generated WS client

I am currently experimenting with web services using netbeans and Sun Application Server.
Basically I am creating simple web services using net beans and then deploy them on the app server and then create another pfoject with web service reference to that web service to invoke the service.
My problem is when a project is deliverd to the production site the the client applications web service reference will need to be configured to refer to the production web service address. But when I looked at the generated web service client code the address is hard coded.
How can I change the address to the web service of a web service reference created in net beans either using some configuration file (without having to recompile the client) or at runtime.
Thanks in advance

bump...

Problem in accessing the Web Service using standalone Java Client

Dear Friends,
Hi,
I have an active web service and I have tested the same with XML Spy and Apache Axis and is giving me the output perfectly. For the same, I have developed a standalone Java client but getting problem in fetching the output.
The Exception is :
<Jan 4, 2006 5:54:16 PM GMT+05:30> <Info> <WebService> <BEA-220025> <Handler weblogic.webservice.core.handler.ClientHandler threw
an exception from its handleResponse method.
The exception was:
javax.xml.rpc.JAXRPCException: java.io.IOException: Received a response from url: http://10.20.15.59:18004/amountToWords which did
not have a valid SOAP content-type: text/html;charset=ISO-8859-1. .>
SOAP Fault **************** Exception during processing: java.io.IOException: Received a response from url: http://10.20.15.59:18
004/amountToWords which did not have a valid SOAP content-type: text/html;charset=ISO-8859-1.
(see Fault Detail for stacktrace)
javax.xml.rpc.soap.SOAPFaultException: Exception during processing: java.io.IOException: Received a response from url: http://10.2
0.15.59:18004/amountToWords which did not have a valid SOAP content-type: text/html;charset=ISO-8859-1.
(see Fault Detail for sta
cktrace)
at weblogic.webservice.core.ClientDispatcher.receive(ClientDispatcher.java:313)
at weblogic.webservice.core.ClientDispatcher.dispatch(ClientDispatcher.java:144)
at weblogic.webservice.core.DefaultOperation.invoke(DefaultOperation.java:457)
at weblogic.webservice.core.DefaultOperation.invoke(DefaultOperation.java:443)
at weblogic.webservice.core.rpc.CallImpl.invoke(CallImpl.java:566)
at weblogic.webservice.core.rpc.CallImpl.invoke(CallImpl.java:419)
at HelloClient.main(HelloClient.java:100)
I have tried some ways to set the content type explicitly but the results are same(throwing an exception).
I appreciate you all for helping me out of this.
Thanks
VR

Hi Amit
We also have this issue with weblogic webservices. Did you get any resolution for this issue.
When the service is executed for lesser number of hits, all the responses are processed properly. But as load (Number of hits for the same service) increases, few responses are failed to be parsed in the web service client. We could confirm that the producer responds with proper content type (text/xml)
Any help or pointers will be greatly appreciated.
Thanks,
Finny

What is the steps to create the web service client

I'm quite new to web service and currently need to work on a web application that will call web service by passing the request data. Then will handle the response data. Following are questions that I would like to get your advice.
First, should I manually develop a schema? The request data will be passed as some element type (I thought a class should be generated and put in the class path), which will be some class with set/get(). Then I will use the schema to get a jar that contains the class file by using the xmlbean? Any example or suggestion on this?
Secondly, how does the java code in web application send/get the request/response data to/from the web service. Your example will greatly help.
I read article about WSDL and Schema and Soap. Get very confused on what really should be to follow step by step. Thanks in advance for your help!

I propose that you start with some introductory tutorials. At seekda you will find two tutorials for newbies:
1) [Finding and Testing Web Services|http://seekda.com/blog/write-your-first-web-services-client-%e2%80%93-part-1-finding-and-testing-services/]
2) [Using Web Services|http://seekda.com/blog/write-your-first-web-services-client-part-2-using-services/]
The second tutorial actually addresses most of your questions.
Greetings,
Michal

Getting SOAPFaultException while Calling the web service

Hi All,
I am using jdev 11g 1.5. I am calling OID process , for which i have created web service proxy. On command button, i hv calling Action Listener and inside that method,i am fetching some data with three view object and setting that value to ODI Webservice class.Then, after that I am calling main proxy method to call the ODI Process through Web service .
For the one user, it is working fine. Take all the value and invoking the ODI Process Web service but If we access the same thing for two users at a times from different system or browser then the first user was being processed and the second request was not processed and resulted in error.
javax.xml.ws.soap.SOAPFaultException: A message was added that is not valid. However, the operation context was
complete.
        at com.sun.xml.ws.fault.SOAP11Fault.getProtocolException(SOAP11Fault.java:197)
        at com.sun.xml.ws.fault.SOAPFaultBuilder.createException(SOAPFaultBuilder.java:122)
        at com.sun.xml.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:125)
        at com.sun.xml.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:95)
        at com.sun.xml.ws.client.sei.SEIStub.invoke(SEIStub.java:136)
        at $Proxy272.invokeScenario(Unknown Source)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:597)
        at weblogic.wsee.jaxws.spi.ClientInstanceInvocationHandler.invoke(ClientInstanceInvocationHandler.java:84)
        at $Proxy270.invokeScenario(Unknown Source)
        at com.test.aaa.CallToODI.invokeODIProcess1_dev(CallToODI.java:5019)
        at com.test.aaa.CallToODI.invokeODIProcess1(CallToODI.java:4652)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:597)
        at com.sun.el.parser.AstValue.invoke(Unknown Source)
        at com.sun.el.MethodExpressionImpl.invoke(Unknown Source)
        at org.apache.myfaces.trinidadinternal.taglib.util.MethodExpressionMethodBinding.invoke
(MethodExpressionMethodBinding.java:53)
        at org.apache.myfaces.trinidad.component.UIXComponentBase.broadcastToMethodBinding
(UIXComponentBase.java:1256)
        at org.apache.myfaces.trinidad.component.UIXCommand.broadcast(UIXCommand.java:183)
        at oracle.adf.view.rich.component.fragment.ContextSwitchingComponent$1.run
(ContextSwitchingComponent.java:92)
        at oracle.adf.view.rich.component.fragment.ContextSwitchingComponent._processPhase
(ContextSwitchingComponent.java:361)
        at oracle.adf.view.rich.component.fragment.ContextSwitchingComponent.broadcast
(ContextSwitchingComponent.java:96)
        at oracle.adf.view.rich.component.fragment.UIXInclude.broadcast(UIXInclude.java:102)
        at oracle.adf.view.rich.component.fragment.ContextSwitchingComponent$1.run
(ContextSwitchingComponent.java:92)
        at oracle.adf.view.rich.component.fragment.ContextSwitchingComponent._processPhase
(ContextSwitchingComponent.java:361)
        at oracle.adf.view.rich.component.fragment.ContextSwitchingComponent.broadcast
(ContextSwitchingComponent.java:96)
        at oracle.adf.view.rich.component.fragment.UIXInclude.broadcast(UIXInclude.java:96)
        at javax.faces.component.UIViewRoot.broadcastEvents(UIViewRoot.java:475)
        at javax.faces.component.UIViewRoot.processApplication(UIViewRoot.java:756)
        at oracle.adfinternal.view.faces.lifecycle.LifecycleImpl._invokeApplication(LifecycleImpl.java:788)
        at oracle.adfinternal.view.faces.lifecycle.LifecycleImpl._executePhase(LifecycleImpl.java:306)
        at oracle.adfinternal.view.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:186)
        at javax.faces.webapp.FacesServlet.service(FacesServlet.java:265)
        at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
        at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
        at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:300)
        at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
        at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
        at oracle.adf.model.servlet.ADFBindingFilter.doFilter(ADFBindingFilter.java:205)
        at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
        at oracle.adfinternal.view.faces.webapp.rich.RegistrationFilter.doFilter(RegistrationFilter.java:106)
        at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl$FilterListChain.doFilter
(TrinidadFilterImpl.java:446)
        at oracle.adfinternal.view.faces.activedata.AdsFilter.doFilter(AdsFilter.java:60)
        at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl$FilterListChain.doFilter
(TrinidadFilterImpl.java:446)
        at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl._doFilterImpl(TrinidadFilterImpl.java:271)
        at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl.doFilter(TrinidadFilterImpl.java:177)
        at org.apache.myfaces.trinidad.webapp.TrinidadFilter.doFilter(TrinidadFilter.java:92)
        at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
        at oracle.security.jps.ee.http.JpsAbsFilter$1.run(JpsAbsFilter.java:111)
        at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:313)
        at oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUtil.java:413)
        at oracle.security.jps.ee.http.JpsAbsFilter.runJaasMode(JpsAbsFilter.java:94)
        at oracle.security.jps.ee.http.JpsAbsFilter.doFilter(JpsAbsFilter.java:161)
        at oracle.security.jps.ee.http.JpsFilter.doFilter(JpsFilter.java:71)
        at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
        at oracle.security.jps.ee.http.JpsAbsFilter$1.run(JpsAbsFilter.java:111)
        at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:313)
        at oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUtil.java:413)
        at oracle.security.jps.ee.http.JpsAbsFilter.runJaasMode(JpsAbsFilter.java:94)
        at oracle.security.jps.ee.http.JpsAbsFilter.doFilter(JpsAbsFilter.java:161)
        at oracle.security.jps.ee.http.JpsFilter.doFilter(JpsFilter.java:71)
        at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
        at oracle.dms.servlet.DMSServletFilter.doFilter(DMSServletFilter.java:136)
        at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
        at weblogic.servlet.internal.RequestEventsFilter.doFilter(RequestEventsFilter.java:27)
        at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
        at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.wrapRun
(WebAppServletContext.java:3723)
        at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run
(WebAppServletContext.java:3689)
        at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
        at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
        at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2285)
        at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2184)
        at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1459)
        at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
        at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)Any one please help me on this.
Thanks
ruzz
Edited by: ruzz on Aug 17, 2012 9:07 AM
Edited by: ruzz on Aug 19, 2012 10:41 PM

thanks for ur reply...
yes. i have checked that line.
See Frank, what is happening, If i have opened the Url in two browser and submitting the button to give the call to ODI process that is done by the web service proxy internally. Then there should be two request and it is taking the two request. But what is happening is that for the first request,it's collect the data and give the call to ODI process and for the second request , it's collect the data but calling to ODI process time it give the error. i am not able to get why this is happening.Same code for the first request, it is working and for the second request, it gv the exception.
Can u please help me on this.
thanks
Ruzz
Edited by: ruzz on Aug 20, 2012 9:25 PM

Create a JSP client to access Web Services

Hi,
I am working on a JSP client in WL 8.1 to access a non-WebLogic web service, with it's WSDL URL. I am trying to run the sample code from the WebLogic web services web site in my JSP but am running into errors with the Service class from JAX-RPC. Here's my JSP code:
<%@page contentType="text/html"
import="java.net.URL, java.util.*, javax.xml.rpc.ServiceFactory, javax.xml.rpc.Service, javax.xml.rpc.*, javax.xml.rpc.Call, javax.xml.rpc.ParameterMode, javax.xml.namespace.QName, javax.xml.*"
%>
<%
ServiceFactory factory = ServiceFactory.newInstance();
// define qnames
String targetNamespace = "http://www.themindelectric.com/" + "wsdl/net.xmethods.services.stockquote.StockQuote/";
QName serviceName = new QName(targetNamespace, "net.xmethods.services.stockquote.StockQuoteService");
QName portName = new QName(targetNamespace, "net.xmethods.services.stockquote.StockQuotePort");
QName operationName = new QName("urn:xmethods-delayed-quotes", "getQuote");
URL wsdlLocation = new URL("http://services.xmethods.net/soap/urn:xmethods-delayed-quotes.wsdl");
// create service
Service service = factory.createService(wsdlLocation, serviceName);
// create call
Call call = service.createCall(portName, operationName);
// invoke the remote web service
Float result = (Float) call.invoke(new Object[] { "BEAS" });
//The result is <%= result %>
%>
<html>
<body>
testing the web service... 
The result is <%= result %>
</body>
</html>
And here's the error. I am not able to create the service using the "Service" class. Any idea what's wrong in my code and how to fix it? I am running it from my domain. Am I missing any JAR files or any CLASSPATH entries?
Thanks in advance for your help.
Error Message below:
<Aug 26, 2005 2:53:25 PM CDT> <Error> <HTTP> <BEA-101020> <[ServletContext(id=33
443136,name=repairApp,context-path=/repairApp)] Servlet failed with Exception
javax.xml.rpc.JAXRPCException: failed to create service
at weblogic.webservice.core.rpc.ServiceImpl.getWebService(ServiceImpl.ja
va:118)
at weblogic.webservice.core.rpc.ServiceFactoryImpl.createService(Service
FactoryImpl.java:42)
at jsp_servlet.__main._jspService(__main.java:150)
at weblogic.servlet.jsp.JspBase.service(JspBase.java:33)
at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run
(ServletStubImpl.java:996)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubIm
pl.java:419)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubIm
pl.java:463)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubIm
pl.java:315)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationActio
n.run(WebAppServletContext.java:6452)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(Authenticate
dSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:
118)
at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppSe
rvletContext.java:3661)
at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestIm
pl.java:2630)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178)
Message was edited by:
sri_bali
Message was edited by:
sri_bali
Message was edited by:
sri_bali

Hi
Were you able to resolve this issue. Can you email me on [email protected] for the same
Thanks
Shilpi

How to access the Web Service Browser

Hi,
I need to access the Web Service Browser to generate a Web Service Description.
How can I do it?
I use the follow url:
http://<host_name>:<port_number>/sap/bc/bsp/sap/WebServiceBrowser/search.html?sap-client=<relevant_client>
but I can't say how to determine values for the three placeholders.
Help me please.
THANKS

Hi Andrea,
you can access the web services in sap transaction SICF. Then right click on the
service and choose "test". The hostname is the host on where the sap system
runs.
The port ´number can be seen in transaction SMICM -> shift + F1. Here you can see
the portnumer assigned to the HTTP protocol.
And the client is the sap client (standard client) for which the service is configured.
Hope this helps.
KR,
Andreas

Access to MySql Database in the Web Service

Hi all,
In my j2me web service project, i want to access to MySql database in the web service and
my installation is
Tomcat 5.0 for Java WSDP,
Java Web Services Developer Pack 1.5,
MySql Server 5.0 and environment variables are adjusted...
server.xml where is in "C:\tomcat50-jwsdp\conf" is adjusted like this

<Realm className="org.apache.catalina.realm.JDBCRealm"
 debug="99"
 driverName="com.mysql.jdbc.Driver"
 connectionURL="jdbc:mysql://localhost:3306/erendb"
 connectionName="root"
 connectionPassword=""
/>
but i have not access to MySql database in the web service yet...
please help...

Hi Luis,
If you see closely, the productID is actually a concatenation of the areaID and the productID. The reasoning here is that a product can be in multiple nodes of the product catalog and one would need to specify the product on a particular node for the direct URL to work.
On a client site, we came up with a better solution by creating a new FM to retrieve the specific areaID and productID for a product. This FM could be called by extending the webshop. Then a .NET program was written to re-direct a shortened form of the URL to the long URL and therefore the specific product in the product catalog. Eg.: http://yyyyy.com/b2c/b2c/product would be automatically redirected to http://yyyyy.com/b2c/b2c/init.do?shop=<shop name>&areaID=<area Guid>&productID=<product Guid>, something similar to the concept behind "tinyurl.com". A point to remember here is that this would work only for the B2C webshop.
Hope this helps.
Cheers,
Ashok.

Oracle EBS throwing exception while invoking the web service

Hi,
When I try to invoke the web service through SOAPUI it is working perfectly fine. however when I try to call it using a .net client. I am getting the below exception:
oracle.apps.fnd.soa.util.SOAException: ServiceProcessingError: System ErrorServiceGenerationError: Error in Creating Response MessageServiceGenerationError: Error in getting translated error messagenull.
Please help me.
Thanks,
Manish

Hi Manish,
Please check notes:
R12.1.1: ISG BPEL Calls Results in java.net.sockettimeoutexception & oracle.apps.fnd.soa.util.SOAException (Doc ID 1103755.1)
"Error in getting translated error messagenull" When Invoking a web service from SOAP UI (Doc ID 1507313.1)
Thanks &
Best Regards,
Asif

Error in browser while testing the web service

Hi all
plz help me out in the following problem.
i have generated a simple web services program using netbean. while i am testing the web service i am getting the following error in the browser
Exceptions details : java.lang.RuntimeException: Service Class not generated as expected
javax.servlet.ServletException: java.lang.RuntimeException: Service Class not generated as expected at com.sun.enterprise.webservice.monitoring.WebServiceTesterServlet.initializePort(WebServiceTesterServlet.java:546) at com.sun.enterprise.webservice.monitoring.WebServiceTesterServlet.doGet(WebServiceTesterServlet.java:158) at com.sun.enterprise.webservice.monitoring.WebServiceTesterServlet.invoke(WebServiceTesterServlet.java:104) at com.sun.enterprise.webservice.JAXWSServlet.doGet(JAXWSServlet.java:233) at javax.servlet.http.HttpServlet.service(HttpServlet.java:707) at javax.servlet.http.HttpServlet.service(HttpServlet.java:820) at org.apache.catalina.core.ApplicationFilterChain.servletService(ApplicationFilterChain.java:397) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:278) at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:566) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:536) at org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:240) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:179) at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:566) at com.sun.enterprise.web.WebPipeline.invoke(WebPipeline.java:73) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:182) at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:566) at com.sun.enterprise.web.VirtualServerPipeline.invoke(VirtualServerPipeline.java:120) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:939) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:137) at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:566) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:536) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:939) at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:239) at com.sun.enterprise.web.connector.grizzly.ProcessorTask.invokeAdapter(ProcessorTask.java:667) at com.sun.enterprise.web.connector.grizzly.ProcessorTask.processNonBlocked(ProcessorTask.java:574) at com.sun.enterprise.web.connector.grizzly.ProcessorTask.process(ProcessorTask.java:844) at com.sun.enterprise.web.connector.grizzly.ReadTask.executeProcessorTask(ReadTask.java:287) at com.sun.enterprise.web.connector.grizzly.ReadTask.doTask(ReadTask.java:212) at com.sun.enterprise.web.connector.grizzly.TaskBase.run(TaskBase.java:252) at com.sun.enterprise.web.connector.grizzly.WorkerThread.run(WorkerThread.java:75) Caused by: java.lang.RuntimeException: Service Class not generated as expected at com.sun.enterprise.webservice.monitoring.WebServiceTesterServlet.initializePort(WebServiceTesterServlet.java:521) ... 29 more
regards
mina

Check this guide for creating a correct WSDL:
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/40611dd6-e66e-2910-f383-e80fb44f9cd4
User user need the role SAP_XI_APPL_SERV_USER
Regards
Stefan

Handling of SOAP Faults in SOAP Clients consuming PI Web services

Hi there,
the following is in regards to SOAP fault error handling in a SOAP client that consumes a Web Service published by PI.
I have been reading a number of threads and blogs in regards to this topic and I am still left with some open questions which I hope to get some final answersclarifications through this thread.
In particular the blogs
Handling Web Service SOAP Fault Responses in SAP NetWeaver XI - Handling Web Service SOAP Fault Responses in SAP NetWeaver XI
XI: Propagation of meaningful error information to SOAP Client - XI: Propagation of meaningful error information to SOAP Client
have caused by attention.
Both of these threads are realating to the Fault Message type one can use to return errors back to a SOAP Client (.Net, Java, etc.).
In our scenario we published a number of Web Services through PI that provide functionality to integrate with an R3 back-end system using inbound ABAP Proxies.
The services are standardised and will be consumed by a number of .NetJava applications and systems. The reason for the use of ABAP proxies is the customer specific application logic that is executed in the backend system. The Web services are synchronous and don't use ccBPM in the middle. Transformations are performed in PI combined with various lookups to set default values before the message is passed into the ABAP Framework of the R3 back-end system. The lookups are done against the R3 back-end system using the PI RFC Lookup feature.
The inbound proxies currently return application errors as part of the response message back to the SOAP client. For more critical errors we introduced the use of Fault message types as the method to return the information back to the SOAP Client. This is all working satisfactory.
The questions I have are as follows.
1. When an error occurs at the IE level (e.g. mapping error), ABAP Proxy framework level (e.g. conversion from XML to ABAP format) or Adapter Framework level (Adapter releated error) a different SOAP fault message structure is returned to the SOAP Client than the one used for the application errors. The SOAP fault message structure used in this case is the standard SOAP fault used by PI to return system errors back to the caller. For those SOAP fault messages there is no payload generated that could be mapped to the SOAP fault structure used for the application errors. This would be preferrable as there would be only one Fault message structure used for both inbound ABAP proxy generated fault messages and PI generated fault messages.
Also the error messages generated by PI can be quite cryptic and difficult to interpret at the client end and could be filtered ranslated during message mapping if the payload of the PI generated SOAP fault message could be accessed in a message mapping.
Point 3 of the above thread 2759 indicates that this would be possible but doesn't outline how. Could somebody please clarify this for me as I don't believe that this is really possible ???.
My idea instead was to use the PI SOAP fault message structure to also return application errors. Therefore I would create a Fault message type that matches the PI SOAP fault structure. This would enable the SOAP Client to handle only one SOAP Fault error structure. Would that be something to look into instead ?????.
2. We have been looking at using the integrated WEB AS SOAP adapter instead of using the AF Sender SOAP adapter. While playing with this we encountered differences in the content returned through the SOAP fault generated by PI. A sample is below. Shouldn't the content of these SOAP faults be the same if the error that caused it is the same. Also the SOAP fault returned by the IE SOAP adapter is much more useful in this particular case. Both errors below are the same, a conversion error from XML to ABAP took place in the inbound ABAP proxy framework of the back-end system.
SOAP fault returned when using SOAP Sender adapter of AF
<!see the documentation>
<SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
 <SOAP:Body>
 <SOAP:Fault>
 <faultcode>SOAP:Server</faultcode>
 <faultstring>Server Error</faultstring>
 <detail>
 <s:SystemError xmlns:s="http://sap.com/xi/WebService/xi2.0">
 <context>XIAdapter</context>
 <code>ADAPTER.JAVA_EXCEPTION</code>
 <text>com.sap.aii.af.ra.ms.api.DeliveryException: XIProxy:PARSE_APPLICATION_DATA:
 at com.sap.aii.adapter.xi.ms.XIEventHandler.onTransmit(XIEventHandler.java:455)
 at com.sap.aii.af.ra.ms.impl.core.queue.consumer.CallConsumer.onMessage(CallConsumer.java:134)
 at com.sap.aii.af.ra.ms.impl.core.queue.Queue.run(Queue.java:916)
 at com.sap.aii.af.ra.ms.runtime.MSWorkWrapper.run(MSWorkWrapper.java:56)
 at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
 at java.security.AccessController.doPrivileged(Native Method)
 at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
 at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)</text>
 </s:SystemError>
 </detail>
 </SOAP:Fault>
 </SOAP:Body>
</SOAP:Envelope>
SOAP fault using integrated SOAP adapter of PI IE
<SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
 <SOAP:Body>
 <SOAP:Fault>
 <faultcode>SOAP:Server</faultcode>
 <faultstring>System Error</faultstring>
 <detail>
 <s:SystemError xmlns:s="http://sap.com/xi/WebService/xi2.0">
 <context/>
 <code>ABAP.PARSE_APPLICATION_DATA</code>
 <text>Error during XML => ABAP conversion (Request Message; error ID: CX_ST_DESERIALIZATION_ERROR; (/1SAI/TXSBE20FF604BAFEF8D990A XML Bytepos.: 564 XML Path: ns1:CreatePORequest(1)POHEADER(2)COMP_CODE(1) Error Text: Data loss occurred when converting ############################## Kernel ErrorId: CONVT_DATA_LOSS))</text>
 </s:SystemError>
 </detail>
 </SOAP:Fault>
 </SOAP:Body>
</SOAP:Envelope>
I have been reading threads for hours without being able to find one that answers questions 1 or provides a blog that outlines the approach one should take for error handling in SOAP clients that consume PI Web Services (and covers both PISystem generated faults and faults raised in Proxies).
There may already be a blog or thread and I just missed it.
Any comments are welcome.
Thanks. Dieter

Hi Dieter,
As Bhavesh already mentioned fault messages are used for application errors. The same is described in SAP XI help:
http://help.sap.com/saphelp_nw04/helpdata/en/dd/b7623c6369f454e10000000a114084/frameset.htm
In case of system error (e.g. field length too long in proxy call or error in XI/PI mapping) there seems to be no standard way of handling it and propagating the response to the consumer of webservice.
Each system error is not recognized by SOAP adapter and SOAP adapter exception is raised.
The only bizzare solution that I can see is developing an adapter module and transport wrong message to standard fault message before delivering it to adapter engine:
http://help.sap.com/saphelp_nw04/helpdata/en/a4/f13341771b4c0de10000000a1550b0/frameset.htm
Kind regards,
Wojciech
btw nice thread

Error during invoking the web service

hi,
i am using axis 1.2.1 & tomcat-5.0.28
when i am trying to invoke the web service i am getting the error.
i am passing all the parameters..then also it is giving the error.i have used the wsdl file to generate the stubs (using wsdl2java tool).the web service is in remote system.
anybody knows Please let me know the soln.
thanks in advance
the error:
Exception in thread "main" AxisFault
faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Client
faultSubcode:
faultString: JAXRPCTIE01: caught exception while handling request: deserialization error: java.lang.NumberFormatException: For input string: ""
faultActor:
faultNode:
faultDetail:
{http://xml.apache.org/axis/}stackTrace:JAXRPCTIE01: caught exception while handling request: deserialization error: java.lang.NumberFormatException: For input string: ""

1. Does your network have a proxy ? - if so, configure the proxy details in the SOAP adapter.
2. Does the WS expect any credentials? - if so configure the same in the adapter.
More: /people/shabarish.vijayakumar/blog/2008/01/08/troubleshooting--rfc-and-soap-scenarios-updated-on-20042009

Servlet as a client to the web-service

Similar Messages

Maybe you are looking for