Deployable web service proxies

Hi,
my understanding of deployable proxies is that their implementation is actually generated at deploy using J2EE Libraries of the target server . Since the deployable proxy implementation is retreived through the JNDI, I am led to beleive there is some container management done regarding the deployable proxy instances. Exp : a pool of proxy objects .
Am I correct ? Can some tuning be done ?
Can you give examples of changes that deployable proxy's tolerate compared to standalone proxys ? The only thing I can think of is a change in the j2ee server version or something like that. In the case the service definition (wsdl) changes ... both type of proxys are rendered useless... or aren't they.
Other than this, the only other advantage I see to deployable proxies is the fact you can manage their security in the web service security service.
Thank you

Ken,
I think you are looking for server environment variables. I know when I was working with tomcat, I made the changes within server.xml and they differed from dev to test to prod, but the names were the same. This way within your code you can get the cotext lookup the variable and use it instead.
If this is what you are looking for, let me know. I need the same thing on SAP Netweaver and haven't got to it, but will be getting to it next.
Nathan.

Similar Messages

Reusing deployable web service proxies

Hi ,
I am new to CE 7.1 and am wondering about reusing deployable web service proxies.
In this link , it is written that
"The Web service client and the Web service proxy must be in the same EAR and in the same module (EJB or Dynamic Web module)."
http://help.sap.com/saphelp_nwce10/helpdata/en/45/113a1221337249e10000000a155369/content.htm
So what if two applications need to use the same deployable web service proxy ? You shouldn't generate 2 proxies. How do both applications use the same deployable proxy ?
Thank you.

Thierry,
If I understand your question correctly, you have two applications (distributed across two or more DCs) and you want to use the same generated Web Service proxies in both the DCs.
If this is the case and assuming that there are two EJB DCs (one containing the proxies and the other containing the actual WS client implementation) and one deployable App DC (containing reference to the two EJB DCs), then define Public Parts for the proxies and use the same in the required EJB DC. You may refer to my [article |http://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/uuid/d00fc143-5878-2c10-6f87-f868c1ae44e6] that explains this concept in a detailed manner.
Br,
Bala

Problem with Oracle Web Service Proxies reusing classes and exceptions

We have an application that have many web services and we're having a really hard time working with Oracle Web Service Proxy. We have many web services that share the same classes for parameters and exceptions. When we generate de proxy classes, it generates a lot of _LiteralSerializer classes. Because I'm reusing the same classes and exceptions it generates the same _LiteralSerializer classes for this classes and they get replaced. For Example
I have classes A and B and Web Services X and Y that use this classes. When I generate the 2 proxies it generates A_LiteralSerializer and B_LiteralSerializer on the 2 proxies and they get replaced and I get "No serlalizers for A class or B class". This problems repeats a lot of times and this problem is a huge risk for our project. We're using JDeveloper 10.1.3.4.
Is there a way to avoid this with Oracle Web Service Proxies?
Regards,
Néstor

Resolved when I create a deployement profile explicitly.
The Webservice.deploy that gets created automatically when I create a web service was giving this issue.
Thanks
Saikrishna

JAAS Login Module using Deployable Web Service proxy

Hi,
We've created a JAAS Login Module that calls a deployable web service proxy to validate users on Netweaver Portal 2004 SP19. To do this the following steps were taken:
1) created a deployable web proxy named 'SGU_proxy' and uploaded it to server. This project created 2 files: 'SGU_proxy.ear' (the one uploaded) and 'SGU_proxyClientAPI.jar'.
2) created a Java project named 'AgregacaoLoginModule' with a single class to authenticate users, this is the class that calls the web service with the username and password. This project references the deployable web proxy project (Properties > Java Build Path > Projects > checkbox marked next to project SGU_proxy).
3) exported the Java project class, not including the 'SGU_proxyClientAPI.jar'.
4) created a 'J2EE Server Component' > 'Library' project named 'AgregacaoLoginModuleJ2EE'.
On the 'provider.xml' file added 2 jars: 'AgregacaoLoginModule.jar' and 'SGU_proxyClientAPI.jar'. References were made to the standard portal libraries. No references were made to the proxy 'SGU_proxy' or the 'AgregacaoLoginModule' project.
The library was uploaded to the server, everything was ok and no errors were reported.
The login module was configured on the server and is called when users try to acess Portal server.
The problem is that when trying to authenticate users: after getting a reference to the proxy using jndi I get a ClassCastException. Note that this proxy is used in a WebDyn Pro application and is working fine.
The web service client proxy generated the interface 'pt.agregacao.ws.sgu.Servicos' and from jndi I get 'class pt.agregacao.ws.sgu.ServicosImpl'. So this seems to be ok, why the exception?
Is it necessary to had a reference to 'SGU_proxy' on the 'AgregacaoLoginModuleJ2EE' project? If so, how?
Thanks in advance.
Alvaro

Hi,
We've created a JAAS Login Module that calls a deployable web service proxy to validate users on Netweaver Portal 2004 SP19. To do this the following steps were taken:
1) created a deployable web proxy named 'SGU_proxy' and uploaded it to server. This project created 2 files: 'SGU_proxy.ear' (the one uploaded) and 'SGU_proxyClientAPI.jar'.
2) created a Java project named 'AgregacaoLoginModule' with a single class to authenticate users, this is the class that calls the web service with the username and password. This project references the deployable web proxy project (Properties > Java Build Path > Projects > checkbox marked next to project SGU_proxy).
3) exported the Java project class, not including the 'SGU_proxyClientAPI.jar'.
4) created a 'J2EE Server Component' > 'Library' project named 'AgregacaoLoginModuleJ2EE'.
On the 'provider.xml' file added 2 jars: 'AgregacaoLoginModule.jar' and 'SGU_proxyClientAPI.jar'. References were made to the standard portal libraries. No references were made to the proxy 'SGU_proxy' or the 'AgregacaoLoginModule' project.
The library was uploaded to the server, everything was ok and no errors were reported.
The login module was configured on the server and is called when users try to acess Portal server.
The problem is that when trying to authenticate users: after getting a reference to the proxy using jndi I get a ClassCastException. Note that this proxy is used in a WebDyn Pro application and is working fine.
The web service client proxy generated the interface 'pt.agregacao.ws.sgu.Servicos' and from jndi I get 'class pt.agregacao.ws.sgu.ServicosImpl'. So this seems to be ok, why the exception?
Is it necessary to had a reference to 'SGU_proxy' on the 'AgregacaoLoginModuleJ2EE' project? If so, how?
Thanks in advance.
Alvaro

Generated Web Service Proxies are not listed in NWA after deployment

Hi everyone,
I have some problems with the generated WS proxies as descriped in SAP Help [Creating Web Service Proxies|https://cw.sdn.sap.com/cw/docs/DOC-104216]). After generation and deplyoment no proxies are listed in the NWA under "SOA Management - Application and Scenario Communication - Single Service Administration". Are there any aditional steps e.g. entries in the deployment descriptors necessary?
Any ideas?
Best regards,
Markus.

Hi Iris,
I think you are in Production Mode enabled Domain, because this option is only available for Dev Mode Domain.
there is one alternate workaround.
Under %BEA_Home% / server / lib
You will find wlstestclient.ear.
and try to access this application and paste the current webservice URL.
Hope this is helpful.
Regards,
Kal

URGENT - Deployable Web Service Proxy gets an unauthorized message

Hello Guys!
I had developed a <i>deployable web service proxy</i> that is called from a servlet. The web service is secured by a basic authentication. My servlet instantiates the proxy and I set the stub like the code bellow:
Maintenance myMaintenance = (Maintenance)ctx.lookup("java:comp/env/MaintenanceWSProxy");
MaintenanceViDocument port = (MaintenanceViDocument)myMaintenance.getLogicalPort("MaintenancePort_Document", MaintenanceViDocument.class);
port._setProperty("javax.xml.rpc.security.auth.username", "user");
port._setProperty("javax.xml.rpc.security.auth.password", "password");
But when I call the servlet, an exception is thrown:
407 - Unauthorized
Somebody knows what is happened?
Thanks a lot!
Best regards,
Marcelo

Hello Marcelo,
i've got an impression that the return error code is related to servlet itself.
Was the servlet deployed as a portal application or as pure j2ee (via SDM or via portal support page)?
Are you accesing it through portal framework or by a direct link to j2ee application?
If it is an portal application - you need to set security policy for iView or for the application (depends on the way you use it. Via iView or via direct link)
If it is an pure j2ee application, then you can define your security roles within the project. First of all, check those settings. Second step is done in VisualAdmin, where you map objects from UME to your security role defined in project.
hope it helps.
regards
mz

Generating web service proxies

Hi,
Is it best practice to generate web service proxies in different packages? Or is it better to let JDeveloper use the namespaces in the XSDs to create the packages?
I am currently doing the former. The problem is that if the generated proxy class refers to the same XSD, but is in a different package, I will have to convert my custom classes multiple times into the generated proxy classes. Is this the best way to do it?
Or should shared XSDs among multiple WSDLs be generated into the same package?

I think its better to use Jdev generated packages to avoid any complications.

Creating Java web service Proxies in nwds 7.3

Hi Experts,
I'm trying to consume the WSDL (Which has been generated from PI. ESR) by following the below thread in NWDS 7.3 but I'm not successful in doing so.
https://help.sap.com/saphelp_nwesrce/helpdata/en/45/100c6be9f87201e10000000a155369/content.htm
In NWDS 7.0 I could able to do generate Java proxy by creating the project File-->new -->project-->web services-->Deployable Proxy Project--> and Proj name and Finish. Once created it will open in Web services Prospective and appears in Client Explorer and we can create the proxy by right clicking --> new--> client Proxy Definition. I want the same thing in NWDS 7.3 also, but in 7.3 I'm struggling to have the similar steps, I found above help document but it is not that clear. Appreciate if any one has document or point to the right thread which has document/example in performing the sa,e thing in NWDS7.3.
Below is the screenshot from NWDS7.0. But want to do the same in NWDS 7.3

Thank you so much Durga, for providing the documents, really helpful. However I have created the Web dynpro DC as below and had few questions when doing it in NW 7.3 version.
Points which I have performed.
1) Created the Web dynpro Java (Web services) DC and application in NWDS 7.3 version.
2) Created the Model's and imported the WSDL from local/ESR (SAP PI web service)
3) created the Service Groups and which populated Service references
4) Deployed the DC in the AS Java 7.3 and configured the Consumer Service Groups for interacting during run time.
Now my question is can we import multiple WSDL's by creating multiple models as shown in the picture? along with the multiple service groups in the same web dynpro java DC? Will it work?
And if yes, If want to use this model from this (Web services) DC to another DC if I add this as dependency and model to the public parts that will do the trick? or will I have do any other configuration/ settings to use this DC in any other DC? Appreciate if you could take a look at this and advise?

SOAP Web Service Authentication configuration

Hello,
I've got a little problem with Web Service authentication configuration.
I'm working on the SAP NetWeaver CE EHP1 7.11. I also have a XMII application deployed on the server and there are some SOAP Web Services(over XMII Transactions) that require basic authentication.
I use all Web Services in the EJB layer. So, I've generated proxy using SAP NetWeaver as a Web Service Runtime for generation. And Iuse an injection mechanism to get a service implementation:
@WebServiceRef(name="GetBatchListService")
private XacuteWS batchListWS;
In this case I could use Single Service Administration application in the NetWeaver Administrator@SOA Management@Application and Scenario Communication to configure basic authentication for EVERY Web Service. And this configuration disappears after every redeploy.
The question is how and where could I configure authentication for all web services?
I've read a lot of documentation, but, unfortunately, I haven't found needed one. I could see 2 direction of searching now, it might help:
1) Destination: Configure HTTP Destination or Web Service Template Destination and use it in all Web Services proxies somehow.
2) Find Configuration way: Create a configuration group or anything else to configure all services from one screen.
Best Regards,
Dmitry

Dimtris,
If your WSDL url is pointing to the URL of the Adapter Engine as shownin the Hot to Use the SOAP adapter there is no option. You cannot add it to the SOAP Url.
But, if you change the SOAP Url to the Url shown in this blog by Stefan Grube then you can add the user id and pasword to the url by adding sap- user=userid and sap-password = password.
The optin shown ion the blog by Grube can be used as long as you do not have to use SOAP attachments and in this case you would not need both sender SOAP adapter and a sender agreement.
/people/stefan.grube/blog/2006/09/21/using-the-soap-inbound-channel-of-the-integration-engine
Regards
Bhavesh
Regards
Bhavesh

Getting the error while invoking Web services

Hi,
I am getting the error while invoking an webservive method *** follows
{color:#3366ff}2009-01-28 04:49:38.994 Error Occured inMesage Now
2009-01-28 04:49:38.994 javax.xml.rpc.ServiceException: Unable to create Service Factory: oracle.j2ee.ws.client.ServiceFactoryImpl
2009-01-28 04:49:38.995 at javax.xml.rpc.ServiceFactory.newInstance(ServiceFactory.java:75)
2009-01-28 04:49:38.995 at ccaproxy.proxy.ISessionClient.<init>(ISessionClient.java:25)
2009-01-28 04:49:38.995 at oracle.apps.contactCenter.mct.model.connector.cca.CCAInternalConnImpl.cstaMonitorStart(CCAInternalConnImpl.java:86)
2009-01-28 04:49:38.995 at oracle.apps.contactCenter.mct.model.connector.CCAMangConnImpl.cstaMonitorStart(CCAMangConnImpl.java:440)
2009-01-28 04:49:38.995 at oracle.apps.contactCenter.mct.model.connector.CCAConnectionImpl.cstaMonitorStart(CCAConnectionImpl.java:107)
2009-01-28 04:49:38.995 at testcca.Class1.GetConnection(Class1.java:54)
2009-01-28 04:49:38.995 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
2009-01-28 04:49:38.995 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
2009-01-28 04:49:38.995 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
2009-01-28 04:49:38.995 at java.lang.reflect.Method.invoke(Method.java:585)
2009-01-28 04:49:38.995 at oracle.j2ee.ws.server.jaxws.ServiceEndpointRuntime.processMessage(ServiceEndpointRuntime.java:283)
2009-01-28 04:49:38.995 at oracle.j2ee.ws.server.jaxws.ServiceEndpointRuntime.processMessage(ServiceEndpointRuntime.java:147)
2009-01-28 04:49:38.995 at oracle.j2ee.ws.server.jaxws.JAXWSRuntimeDelegate.processMessage(JAXWSRuntimeDelegate.java:403)
2009-01-28 04:49:38.995 at oracle.j2ee.ws.server.provider.ProviderProcessor.doEndpointProcessing(ProviderProcessor.java:1055)
2009-01-28 04:49:38.995 at oracle.j2ee.ws.server.WebServiceProcessor.invokeEndpointImplementation(WebServiceProcessor.java:763)
2009-01-28 04:49:38.995 at oracle.j2ee.ws.server.provider.ProviderProcessor.doRequestProcessing(ProviderProcessor.java:528)
2009-01-28 04:49:38.995 at oracle.j2ee.ws.server.WebServiceProcessor.processRequest(WebServiceProcessor.java:212)
2009-01-28 04:49:38.995 at oracle.j2ee.ws.server.WebServiceProcessor.doService(WebServiceProcessor.java:176)
2009-01-28 04:49:38.995 at oracle.j2ee.ws.server.WebServiceServlet.doPost(WebServiceServlet.java:311)
2009-01-28 04:49:38.995 at javax.servlet.http.HttpServlet.service(HttpServlet.java:738)
2009-01-28 04:49:38.995 at javax.servlet.http.HttpServlet.service(HttpServlet.java:831)
2009-01-28 04:49:38.996 at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:692)
2009-01-28 04:49:38.996 at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:351)
2009-01-28 04:49:38.996 at com.evermind.server.http.HttpRequestHandler.doDispatchRequest(HttpRequestHandler.java:977)
2009-01-28 04:49:38.996 at com.evermind.server.http.HttpRequestHandler.doProcessRequest(HttpRequestHandler.java:878)
2009-01-28 04:49:38.996 at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:676)
2009-01-28 04:49:38.996 at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:644)
2009-01-28 04:49:38.996 at com.evermind.server.http.HttpRequestHandler.serveOneRequest(HttpRequestHandler.java:436)
2009-01-28 04:49:38.996 at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:185)
2009-01-28 04:49:38.996 at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:153)
2009-01-28 04:49:38.996 at oracle.oc4j.network.ServerSocketReadHandler$ClientRunnable.run(ServerSocketReadHandler.java:276)
2009-01-28 04:49:38.996 at oracle.oc4j.network.ServerSocketAcceptHandler.procClientSocket(ServerSocketAcceptHandler.java:223)
2009-01-28 04:49:38.996 at oracle.oc4j.network.ServerSocketAcceptHandler.access$900(ServerSocketAcceptHandler.java:39)
2009-01-28 04:49:38.996 at oracle.oc4j.network.ServerSocketAcceptHandler$AcceptHandlerHorse.run(ServerSocketAcceptHandler.java:841)
2009-01-28 04:49:38.996 at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
2009-01-28 04:49:38.996 at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
2009-01-28 04:49:38.996 at java.lang.Thread.run(Thread.java:595)
{color}{color:#000000}The Scenarios is as follows:
I am having a JCA connector which is calling the CCA Method.
CCA uses the web services for method invocation and i have created the jar file for the web service proxies. teh proxies are of RPC type. I have include the jar file in the connector project for reference.
I have written a webservice client which will get the connection abject and invoke a method which internally invokes the CCA method.
During this time it is giving this error.
Please note that i have included the wsclient-extend.jar file ,wsclient jar file in both the connector project and the client project.
Thanks
Santosh{color}

You have to add the jaxrpc library in the server.xml configuration of your embedded oc4j.
Line:
<import-shared-library name="oracle.ws.jaxrpc"/>
You have to do this twice: in the adf.oracle.domain and the adf.generic.domain shared lib entries.
Then, you have to do this again in the system-application.xml file (only once).
Edited by: remcoscc on Aug 23, 2010 4:30 PM

Web service proxy client class missing

Hi,
I am using Jdev 11g.
I created web service proxy but I cannot find a client class.
Where is a client class jdev created?
This is jdev help I refered;
Designing and Developing Applications > Developing with Web Services > Using Existing Web Services in Applications > Creating Web Service Proxies > Using Web Service Proxies
Thanks

Hi,
I created a client class with jdev10134 and put class in my jdev11g project.
I got following error when run client class
Exception in thread "main" java.lang.Error: Jaxrpc 1.1 method is not supported.
at weblogic.webservice.core.rpc.ServiceFactoryImpl.loadService(ServiceFactoryImpl.java:65)
I found this thread.
"Jaxrpc 1.1 method not supported" when running jdev ws-proxy on weblogic
I checked WLS10.3 release note, it seems supported.
Please could someone help me?
Thanks
Edited by: user10445424 on 2008/11/10 17:21

URGENT **** Need help for JAX-RPC Web Service Proxy deploy to OC4J 10.1.3.5

Hi everyone!
I’m really new to web services.
I’m getting a *500 internal server error* while deploying my JAX-RPC web service Proxy to an Oracle AS, in an OC4J, v. 10.1.3.5.0.
Running my client from my development environment (*jdeveloper 10g, 10.1.3.5.0*) everything functions correctly: from jdeveloper I can contact and use the web service defined by the following endpoint: https://www.medialibrary.it/services/federaMLOL.asmx?WSDL
I created a "try_ws_client.jsp" file that runs correctly from my local development environment jdeveloper (that uses an embedded oc4j, v. 10.1.3.5.0) but fails when run from the test server (Oracle AS, in an OC4J, v. 10.1.3.5.0), getting, as I mentioned a 500 internal server error, a white page in IE but with FF the message says: The’s an error in the servlet .....
Here's how I created the ws proxy and how I’m using it to consume the ws I mentioned.
1. I used the jdeveloper “Create Web Service Proxy” wizard (File > New > Business Tier > Web Services > Web Service Prox) and in the WSDL document URL I put: https://www.medialibrary.it/services/federaMLOL.asmx?WSDL
2. The operation ended without adding nothing to the web.xml file and creating the proxy files. One of them is: FederaMLOLSoapClient.java that have the WS exposed methods (es: public boolean createUser(String) ) + a “main” method with the example how to use this client to consume the WS.
public static void main(String[] args) {
try {
it.reggiocity.provincia.mlol.proxy.FederaMLOLSoapClient myPort = new it.reggiocity.provincia.mlol.proxy.FederaMLOLSoapClient();
System.out.println("calling " + myPort.getEndpoint());
// Add your own code here
} catch (Exception ex) {
ex.printStackTrace();
3. In FederaMLOLSoapClient.java I’ve create the method "tyIt":
public String tryIt(String username) {
try {
it.reggiocity.provincia.mlol.proxy.FederaMLOLSoapClient myPort = new it.reggiocity.provincia.mlol.proxy.FederaMLOLSoapClient();
if(myPort.createUser(String username)) {
return “O.K”;
} else {
return “K.O”;
} catch (Exception ex) {
// logs error
4. I created my try_ws_client.jsp file that creates FederaMLOLSoapClient object and calls the tryIt method, printing the “OK” or “KO” message.
<%@ page import="it.reggiocity.provincia.biblioreggiane.*"%>
<%
String message = "";
FederaMLOLSoapClient obj= new FederaMLOLSoapClient( );
message = obj.tryIt(“AAAAAA70R10H226H”);
%>
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<%@ page contentType="text/html;charset=windows-1252"%>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=windows-1252"/>
<title>prova</title>
</head>
<body><%=message%></body>
</html>
The situation is:
My try_ws_client.jsp runs correctly from my jdeveloper and the user is created while creating app.ear and deploying it to my Oracle AS/OC4J as mentioned above, I get a 500 Internal Server Error.
Any idea to find a solution to this problem?
Please help.
Take care.
John M.

Hi,
you want to build the Web Service, or you want to consume the Service as a client? If the latter, Web client (ADF?) or Java client?
Frank

Problem while importing a web service model.

Hi
I am building a simple send email application using a web service.
While creating a new model i am using following options.
step 1 - Select "Import Adaptive web service model"
step 2 - Select Wsdl Source
2.1 - Local file system or URL
Step 3 - No logical destination
step 4 - choose wsdl file from file system.
Process successfully done and model created.
BUT
when i am trying to run this application it is throwing file not found exception. i.e. not able to locate wsdl file.
java.io.FileNotFoundException: C:\AbysalEmail.wsdl (The system cannot find the file specified)
I am using remote network connection to access NWDS. and in remote drive C: itself i have saned my file.
Then Why it is not able to locate my file.
Please Help me out.
Thanks.

Hi
I have provided in J2EE Engine visual administrator under
Web Services Security -> Dynamic web services proxies
following configuration.
I have created a new Dynamic web service proxie.
And in it under connection settings -> URL i have specified
http://<host>:<port>/
Above is host name and potr from where my WebDynpro application runs.
But my file is located in C:\
I think i am unable to set mapping configuration
from
http://<host>:<port>/
to
C:\
Where shall i ten keep my WSDL file.!!!
Thanks.
Edited by: Saurabh Agarwal on Jul 30, 2008 1:34 PM

Accessing XI Web Service in Web DynPro

Hi Experts,
I have a scenario wherein, I will have to access a Web Service that created in XI.
My Finding still now,
1. I have a web service which is created in XI System.
2. Created a Logical Destination in the Visual Administrator. We have given the wsdl URL, system ID, Client and Basic Authentication Information.
3. When we test the Web Service in the Visual Admin, we get a Message Reponse 200, but the content type says Unknown
4. When we test the Web Service in the SOAP Sonar Web Service Testing Tool, we are getting the correct solution
5. After that, we tried creating an Adaptive Web Service Model, using the WSDL URL.
6. When we deploy the application, we get the following error
Exception on creation of service metadata for WS metadata destination 'POItems' and WS interface 'POitem_WS_OUT'. One possible reason is that the metadata destination 'POItems' has not been properly configured; check configuration
When I tried to access a BAPI that is exposed as a Web Service by default, I end up in the following error
Exception on execution of web service with WSDL URL 'http://mycomp01:1001/sap/bc/soap/wsdl11?services=ZBAPI_POITEM_GETLIST&sap-client=800' with operation 'ZBAPI_POITEM_GETLIST' in interface '{urn ap-com ocument ap:rfc:functions}ZBAPI_POITEM_GETLISTPortType'
I have also tried to create a Deployable Web Service using the WSDL file in the Web Service Perspective. Once I deploy the ear file, it appears in the Visual Admin, but when I try testing it I get an error with Response Code 500
Note: I have tried to create an Adaptive Web Service model for the following Link : http://www.webservicex.net/WeatherForecast.asmx?wsdl that is availbale in the net using a logical destination that refers to the same WSDL URL, the application is working fine.
Server/Studio Config details
J2EE - 7.0
NWDS 2004s SP 12
JDK - 1.4.2_09
Please suggest a solution for the above problem or it would be helpful if you can give links that helps in creating a Web DynPro Application to access the XI Web Service. We have followed as per this Link :
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/b2bc0932-0d01-0010-6d8e-cff1b2f22bc7
Regards,
Mathan MP

Vaishali,
never did this before, but some general ideas:
Do you have an WSDL for that web service? Then simply use your NWDS and select New --> Portal Service --> From WSDL (or similar). What I mean is the following: NWDS can read WSDL files and will automatically generate a proxy for you that actually generates an ordinary portal service. This portal service then can be called by standard means in SAP EP.
Regards,
Dominik

Web services Development

A general question for the group (sorry if this is off-topic, if there's a better
forum for this type of Q let me know).
I'm a web services and web app developer who is new to BEA. In the past I've used
toolkits like Axis for web services and I've always preferred this approach. It
seems to me that using BEA I can develop Web Services in one of two ways. The
'low-level' way where I could use the command line tools (or ant) to create, deploy
and manage the code, or I could use WLW and the nice attribute driven approach.
It strikes me (on first blush) that these techniques are not compatible, so if
I choose one I have to stick with that, and I shouldn't (can't) mix and match
the two.
As a relative newcomer to this community which one should I choose?
Which are people out there using?
Can the approaches me mixed?
What implications does using one or the other have in terms of deployment and
the type of WLS I have installed?
Again sorry if this is off topic, or an RTFM. If either of these is the case pointers
to the FM would be appreciated.
Thanks,
Kevin Jones

I think if you are looking for training in "BEA web services" then do
it the WLW way.
However, if you think your web service may be deployed to a non-BEA
app server, then pick up the standards.
This is true for regular web apps using struts vs. WLW's 'netui'
and JSR 162 vs. WLW Portals as well.
Kevin Jones wrote:
Thanks Michael,
anybody else have any comments?
For example if you were looking for training in BEA web services would you expect
it to be WLW or 'command line' based?
Kevin
"Michael Wooten" <[email protected]> wrote:
Hi Kevin,
The two web services development approaches are for two different audiences,
so
it's up to you to select which is more to your liking :-)
Developers who are familiar with the Apache Axis Web Services Platform,
will find
lots of similarities in the Ant-scrpt based approach that the WLS 8.1
Web Services
Platform uses. This would also be the environment for those that really
like to
see that their code uses classes from a standard, like JAX-RPC or SAAJ.
Workshop is really targeted at developers who are less interested in
the mechanics
of Web service construction, and more interested in what they want the
web service
to do. It offers developers with this mindset, almost complete isolation
from
the technologies associated with web service development (i.e. SOAP,
WSDL, XML,
etc.), while still producing a deployable web service that can interoperate
with
web services created by other Web Service stacks.
Again, both of these approaches have healthy developer audiences, so
I see no
real reason to promote one over the other. Personally, I think it makes
sense
to become adept at both.
All in all, I'd have to say that Workshop makes better use of the developer's
time :-)
Regards,
Mike Wooten
"Kevin Jones" <[email protected]> wrote:
A general question for the group (sorry if this is off-topic, if there's
a better
forum for this type of Q let me know).
I'm a web services and web app developer who is new to BEA. In the past
I've used
toolkits like Axis for web services and I've always preferred this approach.
It
seems to me that using BEA I can develop Web Services in one of twoways.
The
'low-level' way where I could use the command line tools (or ant) to
create, deploy
and manage the code, or I could use WLW and the nice attribute driven
approach.
It strikes me (on first blush) that these techniques are not compatible,
so if
I choose one I have to stick with that, and I shouldn't (can't) mixand
match
the two.
As a relative newcomer to this community which one should I choose?
Which are people out there using?
Can the approaches me mixed?
What implications does using one or the other have in terms of deployment
and
the type of WLS I have installed?
Again sorry if this is off topic, or an RTFM. If either of these isthe
case pointers
to the FM would be appreciated.
Thanks,
Kevin Jones

Deployable web service proxies

Similar Messages

Maybe you are looking for