Migrating SOAP WSDL Defs through environments

Hey
I am using the WsdlGenerator component to allow me to create WSDL defs to the Content Server Services. My .Net apps are using the WSDL's to connect to Web Services to perform a variety of functions...
I have recently moved my processes up from Dev into our UAT environment. I have installed the WsdlGenerator component in UAT, but can't figure out how to move the Wsdl defs up. I tried moving the .wsdl files to the "\weblayout\groups\secure\wsdl\custom" folder on the target server, but my code cannot connect to these webserver defs. For the moment, I have resorted to moving the defs by hand, recreating them in the target environment using the "Soap Wsdl" screen under Administration in the Web Client.
Is there a better way to do it?
BTW - I am using Content Server 7.5 on a Microsoft based environment.
Cheers,
Al

Hi,
It looks HTTP Status code 200. That means you already connected to third party. It may be the reason for response message .
Standard response for successful HTTP requests. The actual response will depend on the request method used. In a GET request, the response will contain an entity corresponding to the requested resource. In a POST request the response will contain an entity describing or containing the result of the action.
Deva

Similar Messages

Export SOAP WSDL's in UCM

Hello All,
I have created WSDL for 'AddCollection' in development env. I can able to create collection (folders) & check-in docs to this collections through a java program using this wsdl. Now i want to export this AddCollection.wsdl file to testing env. I couldn't find any option for exporting & importing soap wsdl's in UCM. (or) I have to generate/create the same structure of collection wsdl in testing env manually, is this right way?
Could anyone can provide some idea to overcome this tasks.
My UCM configuration is
Product Version 10.1.3.3.2 (071031)
Product Build 7.2.2.184
Native Version 7.1.0.1
Thanks.
Regards,
Gowri.

You have several options:
First, check out the <install>/data/soap/custom directory and you might find the definition of your custom wsdl. You could move that over to the new server, wire it in and see if it shows up?
Second, there used to be a class called WsdlMerger.java that would allow you to create a component that would install/update custom wsdl's on target machines. This is of limited use for one or two moves, but if you're creating a component with a lot of reuse it works slick. It does take some work to build out and does require some Java skills. If interested, kick me a note and I'll try to get you the Java class for you to toy around with. jason at corecontentonly dot com.
-Jason
http://www.corecontentonly.com

SOAP/WSDL builder for C programming

Dear guru,
is any possibility or can you give any hint if exist some SOAP/WSDL builder for creating C libraries from SOAP/WSDL and vice versa?
Thanks a lot for help.
Regards,
Roman

Rfcsdk, there is a genh.exe in bin folder, which can be used to generate c headers according to ddic table/struct def (se11).
and, you may use Nco to generate wsdl / c# class desc.
all these two method may use se37 function
RFC_GET_FUNCTION_INTERFACE(RFC_GET_FUNCTION_INTERFACE_US) to get function parameter info(I,E,T...) and for a struct/table use RFC_GET_UNICODE_STRUCTURE to get detailed struct info, you may then generate your sql/c#/c typedef/...
Hope these info can be help, you may reach me at <REMOVED BY MODERATOR>, good luck.
Message was edited by:
Alvaro Tejada Galindo

Issue in migration of Planning artifacts through LCM

Hi,
I am trying to migrate EPMA planning application from development server to production server. I am using LCM for the migration and have taken export of the HSS, EPMA, Planning and FR & WA artifacts. I am now importing these artifacts in to production server, however I can not proceed with migration of Planning artifacts through Migration Wizard as I got stuck on the "Destination" step where I got message as "There is no destination available to migrate".
Please guide me on this...
Thanks & Regards,
AK

Hi John,
Please refer to my comments to reply:
Break down the migration into product areas first, start with HSS and then migrate, then move on to planning and HSS, this should narrow down where the issue is
That is what I am doing - I am migrating the artifacts separately i.e. I migrated the HSS first then migrated EPMA Architectue and at last I tried migrating the Planning artifacts during which I got stuck with selection of "Destination" for Planning artifacts.
+"The planning applications need to exist first on your target environment."+
For this I need to create a planning application manually before migrating, and since my planning application is EPMA enabled application and not a classic application I guess I should not create a planning application manually before starting migration. Please guide me on how can I ensure that planning application exist before migrating the same on to target environment
Thanks & Regards,
AK

Weblogic.soap.wsdl.Remote2WSDL

weblogic.soap.wsdl.Remote2WSDL doesn't create the first line in the JSP:
<% response.setHeader( "Content-Type", "text/xml; charset=utf-8" ); %>
that the wsgen Ant task seems to.
Any clues?

This is not a supported Tool. Anyway, the following seems
to work:
java weblogic.soap.wsdl.Remote2WSDL java.util.Vector /foo/bar
regards,
-manoj
"Johannis Dihayco" <[email protected]> wrote in message
news:[email protected]..
Hi, I'm trying to generate the WSDL JSP using the
weblogic.soap.wsdl.Remote2WSDL
utility of Weblogic 6.1.
However I can't seem the jsp file generated contains nothing.
Do I need to run the utility in a directory containing the ejb jar file? How
is the EJB_interface path specified? (what is
meant specifically by fully qualified class name)?
[att1.html]

IdcService SOAP WSDLs

There are lot of idcServices which are OOTB ..is there a way where I can get the wsdl's for those as there are only few wsdl's available under SOAP wsdls link.

Yes, take a look at this link: http://download.oracle.com/docs/cd/E17904_01/doc.1111/e10807/a01_wsdl_and_soap.htm#sthref1831

Timesheet(time Administartion- Time Sheet) WSDl is throughing error when consumed by SOAP UI

Hi,
Requirement : We are trying to integrate the timesheet(time Administartion->Time Sheet) with external sheet
We had downloaded the WSDL (i.e. Manage Employee Time data) from communication arrangment.
when we try to process the same we are facing the error as mentioned in attachment.
can anyone help me on the same
Regards,
Prasad

Hi Prasad,
if you are testing Cloud WSDL via SOAP UI and any error you can check into Application and User Management --> Business Communication Monitoring --> and from drop down select "Reject Web Service Call" option to know more about your error.
as per you error i thing if Work Assignment 1 is not available or may be leading zero problem, i don't know but you can check the error log into the cloud may be its helpful to you.
Regards,
Mithun

Can we use same SOAP ACTION in different environments?

Hi All,
I have a doubt.
Can we use same SOAP Action URL in different environments i.e suppose say Quality, Production and Pre production.And the Target URL is different in both environments.
If yest what is the impact in different environment.

Hi ,
SOAP action is nothing but operation/method in webservice .
Usually at end system end as a good practice/std they will maintain the same soap action name in all their environments,but it's always better to cross check url and soap action with end system folks before configuring in PI .
We have faced an issue in production some time back ,at target system end they upgraded their server and used new wsdl which is almost similar to existing but one of the operation they duplicated by adding few addition fields but forgot to inform PI system.Though we are using new wsdl but pointed to old soap action .Interface got failed in PROD after investigation we come to know that we are using wrong soap action
Regards
Venkat

Error in consuming a WSDl client through a servlet

Hi Guys,
I have generated a client by consumig an enterprise service wsdl.
I have made a servlet to call the client but i get the error as shown below..
Request your help ASAP.
"Application error occurred during the request procession."
Details: Exception:
javax.servlet.ServletException: javax.xml.ws.WebServiceException: HTTP transport error: java.net.ConnectException: Connection timed out: connect
 at test.TestServlet.doGet(TestServlet.java:66)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
 at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:59)
 at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:31)
 at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:431)
 at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:288)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:387)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:376)
 at com.sap.engine.services.servlets_jsp.filters.ServletSelector.process(ServletSelector.java:85)
 at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
 at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:160)
 at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
 at com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:67)
 at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
 at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
 at com.sap.engine.services.httpserver.filters.ResponseLogWriter.process(ResponseLogWriter.java:60)
 at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
 at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
 at com.sap.engine.services.httpserver.filters.DefineHostFilter.process(DefineHostFilter.java:27)
 at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
 at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
 at com.sap.engine.services.httpserver.filters.MonitoringFilter.process(MonitoringFilter.java:29)
 at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
 at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
 at com.sap.engine.services.httpserver.server.Processor.chainedRequest(Processor.java:308)
 at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.run(Processor.java:221)
 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:137)
 at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:229)
Caused by: javax.xml.ws.WebServiceException: HTTP transport error: java.net.ConnectException: Connection timed out: connect
 at com.sun.xml.ws.util.SOAPConnectionUtil.send(SOAPConnectionUtil.java:107)
 at com.sun.xml.ws.util.SOAPConnectionUtil.sendResponse(SOAPConnectionUtil.java:113)
 at com.sun.xml.ws.protocol.soap.client.SOAPMessageDispatcher.doSend(SOAPMessageDispatcher.java:254)
 at com.sun.xml.ws.protocol.soap.client.SOAPMessageDispatcher.send(SOAPMessageDispatcher.java:137)
 at com.sun.xml.ws.encoding.soap.internal.DelegateBase.send(DelegateBase.java:84)
 at com.sun.xml.ws.client.EndpointIFInvocationHandler.implementSEIMethod(EndpointIFInvocationHandler.java:172)
 at com.sun.xml.ws.client.EndpointIFInvocationHandler.invoke(EndpointIFInvocationHandler.java:106)
 at $Proxy322_10002.salesOrderByIDQueryResponseIn(Unknown Source)
 at test.TestServlet.doGet(TestServlet.java:51)
 ... 30 more
Caused by: HTTP transport error: java.net.ConnectException: Connection timed out: connect
 at com.sun.xml.ws.transport.http.client.HttpClientTransport.getOutput(HttpClientTransport.java:111)
 at com.sun.xml.ws.util.SOAPConnectionUtil.send(SOAPConnectionUtil.java:104)
 ... 38 more
Caused by: java.net.ConnectException: Connection timed out: connect
 at java.net.PlainSocketImpl.socketConnect(Native Method)
 at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
 at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
 at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
 at java.net.Socket.connect(Socket.java:519)
 at java.net.Socket.connect(Socket.java:469)
 at sun.net.NetworkClient.doConnect(NetworkClient.java:157)
 at sun.net.www.http.HttpClient.openServer(HttpClient.java:382)
 at sun.net.www.http.HttpClient.openServer(HttpClient.java:509)
 at sun.net.www.http.HttpClient.<init>(HttpClient.java:231)
 at sun.net.www.http.HttpClient.New(HttpClient.java:304)
 at sun.net.www.http.HttpClient.New(HttpClient.java:316)
 at sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient(HttpURLConnection.java:817)
 at sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:769)
 at sun.net.www.protocol.http.HttpURLConnection.connect(HttpURLConnection.java:694)
 at sun.net.www.protocol.http.HttpURLConnection.getOutputStream(HttpURLConnection.java:861)
 at com.sun.xml.ws.transport.http.client.HttpClientTransport.getOutput(HttpClientTransport.java:105)
 ... 39 more
 Root cause:
javax.xml.ws.WebServiceException: HTTP transport error: java.net.ConnectException: Connection timed out: connect
 at com.sun.xml.ws.util.SOAPConnectionUtil.send(SOAPConnectionUtil.java:107)
 at com.sun.xml.ws.util.SOAPConnectionUtil.sendResponse(SOAPConnectionUtil.java:113)
 at com.sun.xml.ws.protocol.soap.client.SOAPMessageDispatcher.doSend(SOAPMessageDispatcher.java:254)
 at com.sun.xml.ws.protocol.soap.client.SOAPMessageDispatcher.send(SOAPMessageDispatcher.java:137)
 at com.sun.xml.ws.encoding.soap.internal.DelegateBase.send(DelegateBase.java:84)
 at com.sun.xml.ws.client.EndpointIFInvocationHandler.implementSEIMethod(EndpointIFInvocationHandler.java:172)
 at com.sun.xml.ws.client.EndpointIFInvocationHandler.invoke(EndpointIFInvocationHandler.java:106)
 at $Proxy322_10002.salesOrderByIDQueryResponseIn(Unknown Source)
 at test.TestServlet.doGet(TestServlet.java:51)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
 at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:59)
 at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:31)
 at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:431)
 at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:288)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:387)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:376)
 at com.sap.engine.services.servlets_jsp.filters.ServletSelector.process(ServletSelector.java:85)
 at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
 at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:160)
 at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
 at com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:67)
 at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
 at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
 at com.sap.engine.services.httpserver.filters.ResponseLogWriter.process(ResponseLogWriter.java:60)
 at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
 at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
 at com.sap.engine.services.httpserver.filters.DefineHostFilter.process(DefineHostFilter.java:27)
 at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
 at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
 at com.sap.engine.services.httpserver.filters.MonitoringFilter.process(MonitoringFilter.java:29)
 at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
 at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
 at com.sap.engine.services.httpserver.server.Processor.chainedRequest(Processor.java:308)
 at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.run(Processor.java:221)
 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:137)
 at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:229)
Caused by: HTTP transport error: java.net.ConnectException: Connection timed out: connect
 at com.sun.xml.ws.transport.http.client.HttpClientTransport.getOutput(HttpClientTransport.java:111)
 at com.sun.xml.ws.util.SOAPConnectionUtil.send(SOAPConnectionUtil.java:104)
 ... 38 more
Caused by: java.net.ConnectException: Connection timed out: connect
 at java.net.PlainSocketImpl.socketConnect(Native Method)
 at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
 at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
 at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
 at java.net.Socket.connect(Socket.java:519)
 at java.net.Socket.connect(Socket.java:469)
 at sun.net.NetworkClient.doConnect(NetworkClient.java:157)
 at sun.net.www.http.HttpClient.openServer(HttpClient.java:382)
 at sun.net.www.http.HttpClient.openServer(HttpClient.java:509)
 at sun.net.www.http.HttpClient.<init>(HttpClient.java:231)
 at sun.net.www.http.HttpClient.New(HttpClient.java:304)
 at sun.net.www.http.HttpClient.New(HttpClient.java:316)
 at sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient(HttpURLConnection.java:817)
 at sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:769)
 at sun.net.www.protocol.http.HttpURLConnection.connect(HttpURLConnection.java:694)
 at sun.net.www.protocol.http.HttpURLConnection.getOutputStream(HttpURLConnection.java:861)
 at com.sun.xml.ws.transport.http.client.HttpClientTransport.getOutput(HttpClientTransport.java:105)
 ... 39 more
javax.xml.ws.WebServiceException: HTTP transport error: java.net.ConnectException: Connection timed out: connect
 at com.sun.xml.ws.util.SOAPConnectionUtil.send(SOAPConnectionUtil.java:107)
 at com.sun.xml.ws.util.SOAPConnectionUtil.sendResponse(SOAPConnectionUtil.java:113)
 at com.sun.xml.ws.protocol.soap.client.SOAPMessageDispatcher.doSend(SOAPMessageDispatcher.java:254)
 at com.sun.xml.ws.protocol.soap.client.SOAPMessageDispatcher.send(SOAPMessageDispatcher.java:137)
 at com.sun.xml.ws.encoding.soap.internal.DelegateBase.send(DelegateBase.java:84)
 at com.sun.xml.ws.client.EndpointIFInvocationHandler.implementSEIMethod(EndpointIFInvocationHandler.java:172)
 at com.sun.xml.ws.client.EndpointIFInvocationHandler.invoke(EndpointIFInvocationHandler.java:106)
 at $Proxy322_10002.salesOrderByIDQueryResponseIn(Unknown Source)
 at test.TestServlet.doGet(TestServlet.java:51)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
 at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:59)
 at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:31)
 at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:431)
 at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:288)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:387)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:376)
 at com.sap.engine.services.servlets_jsp.filters.ServletSelector.process(ServletSelector.java:85)
 at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
 at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:160)
 at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
 at com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:67)
 at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
 at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
 at com.sap.engine.services.httpserver.filters.ResponseLogWriter.process(ResponseLogWriter.java:60)
 at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
 at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
 at com.sap.engine.services.httpserver.filters.DefineHostFilter.process(DefineHostFilter.java:27)
 at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
 at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
 at com.sap.engine.services.httpserver.filters.MonitoringFilter.process(MonitoringFilter.java:29)
 at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
 at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
 at com.sap.engine.services.httpserver.server.Processor.chainedRequest(Processor.java:308)
 at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.run(Processor.java:221)
 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:137)
 at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:229)
Caused by: HTTP transport error: java.net.ConnectException: Connection timed out: connect
 at com.sun.xml.ws.transport.http.client.HttpClientTransport.getOutput(HttpClientTransport.java:111)
 at com.sun.xml.ws.util.SOAPConnectionUtil.send(SOAPConnectionUtil.java:104)
 ... 38 more
Caused by: java.net.ConnectException: Connection timed out: connect
 at java.net.PlainSocketImpl.socketConnect(Native Method)
 at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
 at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
 at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
 at java.net.Socket.connect(Socket.java:519)
 at java.net.Socket.connect(Socket.java:469)
 at sun.net.NetworkClient.doConnect(NetworkClient.java:157)
 at sun.net.www.http.HttpClient.openServer(HttpClient.java:382)
 at sun.net.www.http.HttpClient.openServer(HttpClient.java:509)
 at sun.net.www.http.HttpClient.<init>(HttpClient.java:231)
 at sun.net.www.http.HttpClient.New(HttpClient.java:304)
 at sun.net.www.http.HttpClient.New(HttpClient.java:316)
 at sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient(HttpURLConnection.java:817)
 at sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:769)
 at sun.net.www.protocol.http.HttpURLConnection.connect(HttpURLConnection.java:694)
 at sun.net.www.protocol.http.HttpURLConnection.getOutputStream(HttpURLConnection.java:861)
 at com.sun.xml.ws.transport.http.client.HttpClientTransport.getOutput(HttpClientTransport.java:105)
 ... 39 more

Hi Guys,
I have generated a client by consumig an enterprise service wsdl.
I have made a servlet to call the client but i get the error as shown below..
Request your help ASAP.
"Application error occurred during the request procession."
Details: Exception:
javax.servlet.ServletException: javax.xml.ws.WebServiceException: HTTP transport error: java.net.ConnectException: Connection timed out: connect
 at test.TestServlet.doGet(TestServlet.java:66)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
 at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:59)
 at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:31)
 at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:431)
 at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:288)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:387)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:376)
 at com.sap.engine.services.servlets_jsp.filters.ServletSelector.process(ServletSelector.java:85)
 at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
 at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:160)
 at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
 at com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:67)
 at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
 at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
 at com.sap.engine.services.httpserver.filters.ResponseLogWriter.process(ResponseLogWriter.java:60)
 at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
 at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
 at com.sap.engine.services.httpserver.filters.DefineHostFilter.process(DefineHostFilter.java:27)
 at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
 at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
 at com.sap.engine.services.httpserver.filters.MonitoringFilter.process(MonitoringFilter.java:29)
 at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
 at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
 at com.sap.engine.services.httpserver.server.Processor.chainedRequest(Processor.java:308)
 at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.run(Processor.java:221)
 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:137)
 at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:229)
Caused by: javax.xml.ws.WebServiceException: HTTP transport error: java.net.ConnectException: Connection timed out: connect
 at com.sun.xml.ws.util.SOAPConnectionUtil.send(SOAPConnectionUtil.java:107)
 at com.sun.xml.ws.util.SOAPConnectionUtil.sendResponse(SOAPConnectionUtil.java:113)
 at com.sun.xml.ws.protocol.soap.client.SOAPMessageDispatcher.doSend(SOAPMessageDispatcher.java:254)
 at com.sun.xml.ws.protocol.soap.client.SOAPMessageDispatcher.send(SOAPMessageDispatcher.java:137)
 at com.sun.xml.ws.encoding.soap.internal.DelegateBase.send(DelegateBase.java:84)
 at com.sun.xml.ws.client.EndpointIFInvocationHandler.implementSEIMethod(EndpointIFInvocationHandler.java:172)
 at com.sun.xml.ws.client.EndpointIFInvocationHandler.invoke(EndpointIFInvocationHandler.java:106)
 at $Proxy322_10002.salesOrderByIDQueryResponseIn(Unknown Source)
 at test.TestServlet.doGet(TestServlet.java:51)
 ... 30 more
Caused by: HTTP transport error: java.net.ConnectException: Connection timed out: connect
 at com.sun.xml.ws.transport.http.client.HttpClientTransport.getOutput(HttpClientTransport.java:111)
 at com.sun.xml.ws.util.SOAPConnectionUtil.send(SOAPConnectionUtil.java:104)
 ... 38 more
Caused by: java.net.ConnectException: Connection timed out: connect
 at java.net.PlainSocketImpl.socketConnect(Native Method)
 at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
 at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
 at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
 at java.net.Socket.connect(Socket.java:519)
 at java.net.Socket.connect(Socket.java:469)
 at sun.net.NetworkClient.doConnect(NetworkClient.java:157)
 at sun.net.www.http.HttpClient.openServer(HttpClient.java:382)
 at sun.net.www.http.HttpClient.openServer(HttpClient.java:509)
 at sun.net.www.http.HttpClient.<init>(HttpClient.java:231)
 at sun.net.www.http.HttpClient.New(HttpClient.java:304)
 at sun.net.www.http.HttpClient.New(HttpClient.java:316)
 at sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient(HttpURLConnection.java:817)
 at sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:769)
 at sun.net.www.protocol.http.HttpURLConnection.connect(HttpURLConnection.java:694)
 at sun.net.www.protocol.http.HttpURLConnection.getOutputStream(HttpURLConnection.java:861)
 at com.sun.xml.ws.transport.http.client.HttpClientTransport.getOutput(HttpClientTransport.java:105)
 ... 39 more
 Root cause:
javax.xml.ws.WebServiceException: HTTP transport error: java.net.ConnectException: Connection timed out: connect
 at com.sun.xml.ws.util.SOAPConnectionUtil.send(SOAPConnectionUtil.java:107)
 at com.sun.xml.ws.util.SOAPConnectionUtil.sendResponse(SOAPConnectionUtil.java:113)
 at com.sun.xml.ws.protocol.soap.client.SOAPMessageDispatcher.doSend(SOAPMessageDispatcher.java:254)
 at com.sun.xml.ws.protocol.soap.client.SOAPMessageDispatcher.send(SOAPMessageDispatcher.java:137)
 at com.sun.xml.ws.encoding.soap.internal.DelegateBase.send(DelegateBase.java:84)
 at com.sun.xml.ws.client.EndpointIFInvocationHandler.implementSEIMethod(EndpointIFInvocationHandler.java:172)
 at com.sun.xml.ws.client.EndpointIFInvocationHandler.invoke(EndpointIFInvocationHandler.java:106)
 at $Proxy322_10002.salesOrderByIDQueryResponseIn(Unknown Source)
 at test.TestServlet.doGet(TestServlet.java:51)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
 at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:59)
 at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:31)
 at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:431)
 at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:288)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:387)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:376)
 at com.sap.engine.services.servlets_jsp.filters.ServletSelector.process(ServletSelector.java:85)
 at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
 at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:160)
 at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
 at com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:67)
 at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
 at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
 at com.sap.engine.services.httpserver.filters.ResponseLogWriter.process(ResponseLogWriter.java:60)
 at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
 at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
 at com.sap.engine.services.httpserver.filters.DefineHostFilter.process(DefineHostFilter.java:27)
 at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
 at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
 at com.sap.engine.services.httpserver.filters.MonitoringFilter.process(MonitoringFilter.java:29)
 at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
 at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
 at com.sap.engine.services.httpserver.server.Processor.chainedRequest(Processor.java:308)
 at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.run(Processor.java:221)
 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:137)
 at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:229)
Caused by: HTTP transport error: java.net.ConnectException: Connection timed out: connect
 at com.sun.xml.ws.transport.http.client.HttpClientTransport.getOutput(HttpClientTransport.java:111)
 at com.sun.xml.ws.util.SOAPConnectionUtil.send(SOAPConnectionUtil.java:104)
 ... 38 more
Caused by: java.net.ConnectException: Connection timed out: connect
 at java.net.PlainSocketImpl.socketConnect(Native Method)
 at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
 at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
 at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
 at java.net.Socket.connect(Socket.java:519)
 at java.net.Socket.connect(Socket.java:469)
 at sun.net.NetworkClient.doConnect(NetworkClient.java:157)
 at sun.net.www.http.HttpClient.openServer(HttpClient.java:382)
 at sun.net.www.http.HttpClient.openServer(HttpClient.java:509)
 at sun.net.www.http.HttpClient.<init>(HttpClient.java:231)
 at sun.net.www.http.HttpClient.New(HttpClient.java:304)
 at sun.net.www.http.HttpClient.New(HttpClient.java:316)
 at sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient(HttpURLConnection.java:817)
 at sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:769)
 at sun.net.www.protocol.http.HttpURLConnection.connect(HttpURLConnection.java:694)
 at sun.net.www.protocol.http.HttpURLConnection.getOutputStream(HttpURLConnection.java:861)
 at com.sun.xml.ws.transport.http.client.HttpClientTransport.getOutput(HttpClientTransport.java:105)
 ... 39 more
javax.xml.ws.WebServiceException: HTTP transport error: java.net.ConnectException: Connection timed out: connect
 at com.sun.xml.ws.util.SOAPConnectionUtil.send(SOAPConnectionUtil.java:107)
 at com.sun.xml.ws.util.SOAPConnectionUtil.sendResponse(SOAPConnectionUtil.java:113)
 at com.sun.xml.ws.protocol.soap.client.SOAPMessageDispatcher.doSend(SOAPMessageDispatcher.java:254)
 at com.sun.xml.ws.protocol.soap.client.SOAPMessageDispatcher.send(SOAPMessageDispatcher.java:137)
 at com.sun.xml.ws.encoding.soap.internal.DelegateBase.send(DelegateBase.java:84)
 at com.sun.xml.ws.client.EndpointIFInvocationHandler.implementSEIMethod(EndpointIFInvocationHandler.java:172)
 at com.sun.xml.ws.client.EndpointIFInvocationHandler.invoke(EndpointIFInvocationHandler.java:106)
 at $Proxy322_10002.salesOrderByIDQueryResponseIn(Unknown Source)
 at test.TestServlet.doGet(TestServlet.java:51)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
 at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:59)
 at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:31)
 at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:431)
 at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:288)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:387)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:376)
 at com.sap.engine.services.servlets_jsp.filters.ServletSelector.process(ServletSelector.java:85)
 at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
 at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:160)
 at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
 at com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:67)
 at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
 at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
 at com.sap.engine.services.httpserver.filters.ResponseLogWriter.process(ResponseLogWriter.java:60)
 at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
 at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
 at com.sap.engine.services.httpserver.filters.DefineHostFilter.process(DefineHostFilter.java:27)
 at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
 at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
 at com.sap.engine.services.httpserver.filters.MonitoringFilter.process(MonitoringFilter.java:29)
 at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
 at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
 at com.sap.engine.services.httpserver.server.Processor.chainedRequest(Processor.java:308)
 at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.run(Processor.java:221)
 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:137)
 at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:229)
Caused by: HTTP transport error: java.net.ConnectException: Connection timed out: connect
 at com.sun.xml.ws.transport.http.client.HttpClientTransport.getOutput(HttpClientTransport.java:111)
 at com.sun.xml.ws.util.SOAPConnectionUtil.send(SOAPConnectionUtil.java:104)
 ... 38 more
Caused by: java.net.ConnectException: Connection timed out: connect
 at java.net.PlainSocketImpl.socketConnect(Native Method)
 at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
 at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
 at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
 at java.net.Socket.connect(Socket.java:519)
 at java.net.Socket.connect(Socket.java:469)
 at sun.net.NetworkClient.doConnect(NetworkClient.java:157)
 at sun.net.www.http.HttpClient.openServer(HttpClient.java:382)
 at sun.net.www.http.HttpClient.openServer(HttpClient.java:509)
 at sun.net.www.http.HttpClient.<init>(HttpClient.java:231)
 at sun.net.www.http.HttpClient.New(HttpClient.java:304)
 at sun.net.www.http.HttpClient.New(HttpClient.java:316)
 at sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient(HttpURLConnection.java:817)
 at sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:769)
 at sun.net.www.protocol.http.HttpURLConnection.connect(HttpURLConnection.java:694)
 at sun.net.www.protocol.http.HttpURLConnection.getOutputStream(HttpURLConnection.java:861)
 at com.sun.xml.ws.transport.http.client.HttpClientTransport.getOutput(HttpClientTransport.java:105)
 ... 39 more

How do I create only SOAP WSDL bindings when deploying my ESB?

Currently when I use either jDeveloper or the ant deployESBSuitcase task to deploy the ESB that is the entry point to my application I get two bindings in the deployed wsdl. One soap binding that my client will be using and another esb binding. Is it possible to modify the deployment plan to only generate the SOAP binding? Do I need to have the esb binding for an esb that is only used as the entry point to my application? I would prefer to have the wsdl that is exposed to my clients to not have the vendor extensions if possible.
thanks

I have experienced the exact same problem. There is no good solution to these poorly designed and overly complex login protocols. After unsuccessfully trying to retrieve my password or change my password I finally set up a new email account, a new Apple ID and a new iTunes account.
I know it is not a good solution, but it worked.

How to put user comments in WSDL File through webservices

I created one web service application and i deployed and it is running.
Now I want to put comments (like what is the parameters, type) in wsdl file for
each method in my web service.
I am using web logic server 8.1 service pack 2.
Any can give answers to my question

Use the sap-user parameter in the WSDL...for more information refer: /people/stefan.grube/blog/2006/09/21/using-the-soap-inbound-channel-of-the-integration-engine
Regards,
Abhishek.

Webservice soap wsdl generation

Hi Experts,
Please Help Me,
Systems. ThirdParty (PHP Portal) --> SAP PI--> SAP ECC
1: What is best practise to add ThirdParty as business service or business system.
Scenario1: TirdParty Request for emp address based on the emp id here emp address in sap ecc.
i would like to use SOAP TO PI TO RFC (req & res bapis)
2. this scenario thirparty will generate wsdl and import to SAP PI or SAP PI side should generate wsdl.

1. business service
2. you should generate wsdl from sender agreement in SAP PI (Integration Builder)

PHP5 SOAP WSDL and Xcelsius 2008 communication error

Hi,
I wood like to use PHP5 Soap server and WSDL for Xcelsius2008.
Now Xcelsius 2008 can read WSDL parameters, and data from Xcelsius appear in Soap server, but in the Soap Response is the error message:
<?xml version="1.0" encoding="UTF-8"?>
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">
<SOAP-ENV:Body>
<SOAP-ENV:Fault>
 <faultcode>SOAP-ENV:Client</faultcode>
 <faultstring>Bad Request</faultstring>
</SOAP-ENV:Fault>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
My WSDL is here:
http://www.tanit.hu/custimp/wsdl/hello/hello_04.wsdl
My PHP5 Soap Server:
<?php
ini_set("soap.wsdl_cache_enabled","0");
$server = new SoapServer("hello_04.wsdl");
class HelloService{
function doHello($yourName){
 if (strlen(trim($yourName))) {
 return "Hello ".$yourName;
 } else {
 throw new SoapFault("Server","The input parameter is Empty!");
?>
My PHP5 Soap Client (is working properly):
<?php
ini_set("soap.wsdl_cache_enabled","0");
try{
$sClient = new SoapClient('http://www.tanit.hu/custimp/wsdl/hello/hello_04.wsdl');
$response = $sClient->doHello('MyName');
echo $response;
} catch(SoapFault $e){
var_dump($e);
?>
Could somebody help me?
Thx.

OK.
[I found this.|https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/oss_notes_boj/sdn_oss_boj_erq/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/scn_bosap/notes%7B6163636573733d36393736354636443646363436353344333933393338323636393736354637333631373036453646373436353733354636453735364436323635373233443330333033303331333233343330333133373334%7D.do]

Simple SOAP+WSDL example needed

I'm pretty much confused about SOAP and WSDL and can't find a good and simple example. I use Sun One Studio. How do I run some web service example.

You can find some examples:
http://java.sun.com/xml/jaxp/dist/1.0.1/examples/#building
http://newinstance.com/writing/javaxml2/javaxml2_examples.html
http://www.docuverse.com/domsdk/index.html#tutorial
http://www.devx.com/sourcebank/search.asp

WSDL generated through SOAMANAGER cannot be loaded into flex

Guys,
I'm having a problem here where I use soamanager to generate the WSDL for a webservice named: ztestpg_ws.
for some reason, Adobe Flex cannot load it. Any ideas at all????
Here is the WSDL:
<?xml version="1.0" encoding="utf-8" ?>
- <wsdl:definitions targetNamespace="urn:sap-com:document:sap:soap:functions:mc-style" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:http="http://schemas.xmlsoap.org/wsdl/http/" xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/" xmlns:tns="urn:sap-com:document:sap:soap:functions:mc-style" xmlns:wsp="http://schemas.xmlsoap.org/ws/2004/09/policy" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd">
- <wsdl:documentation>
<sidl:sidl xmlns:sidl="http://www.sap.com/2007/03/sidl" />
</wsdl:documentation>
<wsp:UsingPolicy wsdl:required="true" />
- <wsp:Policy wsu:Id="BN_ztestpg_ws">
- <wsp:ExactlyOne xmlns:wsp="http://schemas.xmlsoap.org/ws/2004/09/policy" xmlns:sapsp="http://www.sap.com/webas/630/soap/features/security/policy" xmlns:sp="http://docs.oasis-open.org/ws-sx/ws-securitypolicy/200702" xmlns:wsa="http://www.w3.org/2005/08/addressing" xmlns:wsu="http://schemas.xmlsoap.org/ws/2002/07/utility">
- <wsp:All>
- <sp:TransportBinding>
- <wsp:Policy>
- <sp:TransportToken>
- <wsp:Policy>
<sp:HttpsToken />
</wsp:Policy>
</sp:TransportToken>
- <sp:AlgorithmSuite>
- <wsp:Policy>
<sp:TripleDesRsa15 />
</wsp:Policy>
</sp:AlgorithmSuite>
- <sp:Layout>
- <wsp:Policy>
<sp:Strict />
</wsp:Policy>
</sp:Layout>
</wsp:Policy>
</sp:TransportBinding>
</wsp:All>
</wsp:ExactlyOne>
<saptrnbnd:OptimizedXMLTransfer uri="http://xml.sap.com/2006/11/esi/esp/binxml" xmlns:saptrnbnd="http://www.sap.com/webas/710/soap/features/transportbinding/" wsp:Optional="true" />
</wsp:Policy>
- <wsp:Policy wsu:Id="IF_ztestpg_ws">
- <sapsession:Session xmlns:sapsession="http://www.sap.com/webas/630/soap/features/session/">
<sapsession:enableSession>false</sapsession:enableSession>
</sapsession:Session>
<wsp:ExactlyOne xmlns:wsp="http://schemas.xmlsoap.org/ws/2004/09/policy" xmlns:sapsp="http://www.sap.com/webas/630/soap/features/security/policy" xmlns:sp="http://docs.oasis-open.org/ws-sx/ws-securitypolicy/200702" xmlns:wsa="http://www.w3.org/2005/08/addressing" xmlns:wsu="http://schemas.xmlsoap.org/ws/2002/07/utility" />
</wsp:Policy>
- <wsp:Policy wsu:Id="OP_Ztestpg">
<sapcomhnd:enableCommit xmlns:sapcomhnd="http://www.sap.com/NW05/soap/features/commit/">false</sapcomhnd:enableCommit>
<sapblock:enableBlocking xmlns:sapblock="http://www.sap.com/NW05/soap/features/blocking/">true</sapblock:enableBlocking>
<saptrhnw05:required xmlns:saptrhnw05="http://www.sap.com/NW05/soap/features/transaction/">no</saptrhnw05:required>
<saprmnw05:enableWSRM xmlns:saprmnw05="http://www.sap.com/NW05/soap/features/wsrm/">false</saprmnw05:enableWSRM>
</wsp:Policy>
- <wsdl:types>
- <xsd:schema attributeFormDefault="qualified" targetNamespace="urn:sap-com:document:sap:soap:functions:mc-style">
- <xsd:element name="Ztestpg">
- <xsd:complexType>
<xsd:sequence />
</xsd:complexType>
</xsd:element>
- <xsd:element name="ZtestpgResponse">
- <xsd:complexType>
- <xsd:sequence>
<xsd:element name="Rc" type="xsd:int" />
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:schema>
</wsdl:types>
- <wsdl:message name="Ztestpg">
<wsdl:part name="parameters" element="tns:Ztestpg" />
</wsdl:message>
- <wsdl:message name="ZtestpgResponse">
<wsdl:part name="parameter" element="tns:ZtestpgResponse" />
</wsdl:message>
- <wsdl:portType name="ztestpg_ws">
- <wsp:Policy>
<wsp:PolicyReference URI="#IF_ztestpg_ws" />
</wsp:Policy>
- <wsdl:operation name="Ztestpg">
- <wsp:Policy>
<wsp:PolicyReference URI="#OP_Ztestpg" />
</wsp:Policy>
<wsdl:input message="tns:Ztestpg" />
<wsdl:output message="tns:ZtestpgResponse" />
</wsdl:operation>
</wsdl:portType>
- <wsdl:binding name="ztestpg_ws" type="tns:ztestpg_ws">
- <wsp:Policy>
<wsp:PolicyReference URI="#BN_ztestpg_ws" />
</wsp:Policy>
<soap:binding transport="http://schemas.xmlsoap.org/soap/http" style="document" />
- <wsdl:operation name="Ztestpg">
<soap:operation soapAction="" style="document" />
- <wsdl:input>
<soap:body use="literal" />
</wsdl:input>
- <wsdl:output>
<soap:body use="literal" />
</wsdl:output>
</wsdl:operation>
</wsdl:binding>
- <wsdl:service name="service">
- <wsdl:port name="ztestpg_ws" binding="tns:ztestpg_ws">
<soap:address location="http://jq03a010.esc.win.colpal.com:8035/sap/bc/srt/rfc/sap/ztestpg_ws/321/ztestpg_ws/ztestpg_ws" />
</wsdl:port>
</wsdl:service>
</wsdl:definitions>

the same problem generating Axis2 clients. There is no module extension for:
cannot find a PolicyExtension to process http://www.sap.com/NW05/soap/features/commit/type assertions
cannot find a PolicyExtension to process http://www.sap.com/NW05/soap/features/transaction/type assertions
cannot find a PolicyExtension to process http://www.sap.com/NW05/soap/features/wsrm/type assertions
cannot find a PolicyExtension to process http://www.sap.com/NW05/soap/features/blocking/type assertions
hmm...
Best regards
T. Kis

Migrating SOAP WSDL Defs through environments

Similar Messages

Maybe you are looking for