Client proxy generation problem

Hi All,
I'm trying to create client proxy using given WSDL link in SE80 under enterprise services.
When I enter URL as given WSDL link it is asking for user and password.
When I enter required details (domain name/username) and password, I'm getting an error saying problem with XML generation.
When I access this WSDL link from IE with same user and password I'm able to access this service.
Could some one help me on this issue.
Thanks
Raghavendra

Hi Raja,
I do have similar problem. But If I save the WSDL in local file will it meet my requirement or not I'm not sure about this.
I'm trying to invoke the external web service by creating client proxy in SE80.
which is deployed on some machine. This service will in turn create user account in windows active directory with the details from SAP.
Now when SAP is invoking this service it will ask user and password.
But if I save this in local file will this service will work or not I'm not sure.
Is there anyway if I enter user and password then it will process further.
Let me know your inputs on this.
Regards
Vikram

Similar Messages

ABAP Web Service client proxy - generation problems

Hi!
I tried to create an ABAP web service client proxy for many different web services -
for instance some of that listed at <a href="http://www.xmethods.net/">http://www.xmethods.net/</a> .
Almost on 99% of the WSDLs the client proxy generation failed.
For istance "<extension> not supported", or "<message...> must have at least one part",... .
Could anybody tell me what restrictions are to web services you can create a
ABAP client proxy for ?
In the SAP Web AS Java Stack there is no problem at all to generate a
client proxy for almost all of the xmethod-WebServices !
Is the ABAP Web Service proxy generation for production use ?
Regards
Frank Ruggaber

Resolved through SAP Help. Refer SAP note# 0001403271.

Client Proxy Generation Error

Hi All,
I have a java web-service deployed in Enterprise Portal which I need to consume in a BSP.
Unfortunately, I'm getting an error on client proxy generation:
Proxy generation terminated: Message must have exactly one part
Is anyone familiar with this? The WSDL file says it has been generated by SAP PORTAL ECLIPSE PLUGINS.
Here is the WSDL file:
<?xml version="1.0" encoding="UTF-8" ?>
- 
- 
- <wsdl:definitions name="xCDRServices" targetNamespace="prt:service:com.sap.xcdr.xCDRServices" xmlns:intf="prt:service:com.sap.xcdr.xCDRServices" xmlns:xsd_doc="prt:service:com.sap.xcdr.xCDRServices/DocumentTypes" xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime" xmlns:http="http://schemas.xmlsoap.org/soap/http" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:tns0="http://prt.java.soap/schemas" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:tns2="http://lang.java" xmlns:tns1="http://api.security.sap.com">
- <types>
- <schema xmlns="http://www.w3.org/2001/XMLSchema" targetNamespace="prt:service:com.sap.xcdr.xCDRServices/DocumentTypes" elementFormDefault="qualified">
<element name="checkUserExists_1_param2" nillable="true" type="xsd:string" />
<element name="response_checkUserExists_1" type="xsd:int" />
<element name="getUserRoles_1_param3" nillable="true" type="xsd:string" />
<element name="response_getUserRoles_2" nillable="true" type="xsd:string" />
<element name="getAllRolesInNameSpace_1_param4" nillable="true" type="xsd:string" />
<element name="response_getAllRolesInNameSpace_3" nillable="true" type="xsd:string" />
<element name="assignRoles_2_param5" nillable="true" type="xsd:string" />
<element name="assignRoles_2_param6" nillable="true" type="xsd:string" />
<element name="response_assignRoles_4" nillable="true" type="xsd:string" />
</schema>
- <schema xmlns="http://www.w3.org/2001/XMLSchema" targetNamespace="http://prt.java.soap/schemas" elementFormDefault="qualified">
- <complexType name="PortalSOAPFault">
- <sequence>
<element name="stackTrace" minOccurs="0" maxOccurs="1" type="xsd:string" />
</sequence>
</complexType>
- <complexType name="UMException">
- <complexContent>
- <extension base="tns0:PortalSOAPFault">
- <sequence>
<element name="LocalizedMessage" nillable="true" type="xsd:string" />
<element name="Message" nillable="true" type="xsd:string" />
<element name="NestedException" type="tns0:Throwable" />
</sequence>
</extension>
</complexContent>
</complexType>
- <complexType name="Throwable">
- <complexContent>
- <extension base="tns0:PortalSOAPFault">
<sequence />
</extension>
</complexContent>
</complexType>
<element name="error_UMException" type="tns0:UMException" />
</schema>
</types>
- <wsdl:message name="assignRolesResponse">
<wsdl:part name="response_assignRoles_4" element="xsd_doc:response_assignRoles_4" />
</wsdl:message>
- <wsdl:message name="checkUserExistsRequest">
<wsdl:part name="checkUserExists_1_param2" element="xsd_doc:checkUserExists_1_param2" />
</wsdl:message>
- <wsdl:message name="checkUserExistsResponse">
<wsdl:part name="response_checkUserExists_1" element="xsd_doc:response_checkUserExists_1" />
</wsdl:message>
- <wsdl:message name="getAllRolesInNameSpaceResponse">
<wsdl:part name="response_getAllRolesInNameSpace_3" element="xsd_doc:response_getAllRolesInNameSpace_3" />
</wsdl:message>
- <wsdl:message name="getAllRolesInNameSpaceRequest">
<wsdl:part name="getAllRolesInNameSpace_1_param4" element="xsd_doc:getAllRolesInNameSpace_1_param4" />
</wsdl:message>
- <wsdl:message name="UMException">
<wsdl:part name="error_UMException" element="tns0:error_UMException" />
</wsdl:message>
- <wsdl:message name="getUserRolesRequest">
<wsdl:part name="getUserRoles_1_param3" element="xsd_doc:getUserRoles_1_param3" />
</wsdl:message>
- <wsdl:message name="assignRolesRequest">
<wsdl:part name="assignRoles_2_param5" element="xsd_doc:assignRoles_2_param5" />
<wsdl:part name="assignRoles_2_param6" element="xsd_doc:assignRoles_2_param6" />
</wsdl:message>
- <wsdl:message name="getUserRolesResponse">
<wsdl:part name="response_getUserRoles_2" element="xsd_doc:response_getUserRoles_2" />
</wsdl:message>
- <wsdl:portType name="xCDRServices">
- <wsdl:operation name="checkUserExists" parameterOrder="checkUserExists_1_param2">
<wsdl:input name="checkUserExists_input0" message="intf:checkUserExistsRequest" />
<wsdl:output name="checkUserExists_output0" message="intf:checkUserExistsResponse" />
</wsdl:operation>
- <wsdl:operation name="getUserRoles" parameterOrder="getUserRoles_1_param3">
<wsdl:input name="getUserRoles_input0" message="intf:getUserRolesRequest" />
<wsdl:output name="getUserRoles_output0" message="intf:getUserRolesResponse" />
<wsdl:fault name="com.sap.security.api.UMException" message="intf:UMException" />
</wsdl:operation>
- <wsdl:operation name="getAllRolesInNameSpace" parameterOrder="getAllRolesInNameSpace_1_param4">
<wsdl:input name="getAllRolesInNameSpace_input0" message="intf:getAllRolesInNameSpaceRequest" />
<wsdl:output name="getAllRolesInNameSpace_output0" message="intf:getAllRolesInNameSpaceResponse" />
<wsdl:fault name="com.sap.security.api.UMException" message="intf:UMException" />
</wsdl:operation>
- <wsdl:operation name="assignRoles" parameterOrder="assignRoles_2_param5 assignRoles_2_param6">
<wsdl:input name="assignRoles_input0" message="intf:assignRolesRequest" />
<wsdl:output name="assignRoles_output0" message="intf:assignRolesResponse" />
<wsdl:fault name="com.sap.security.api.UMException" message="intf:UMException" />
</wsdl:operation>
</wsdl:portType>
- <wsdl:binding name="com.sap.portal.prt.soap.xCDRServicesBinding" type="intf:xCDRServices">
<soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http" />
- <wsdl:operation name="checkUserExists">
<soap:operation soapAction="prt:service:com.sap.xcdr.xCDRServices.xCDRServices/checkUserExists0" />
- <wsdl:input name="checkUserExists_input0">
<soap:body use="literal" />
</wsdl:input>
- <wsdl:output name="checkUserExists_output0">
<soap:body use="literal" />
</wsdl:output>
</wsdl:operation>
- <wsdl:operation name="getUserRoles">
<soap:operation soapAction="prt:service:com.sap.xcdr.xCDRServices.xCDRServices/getUserRoles0" />
- <wsdl:input name="getUserRoles_input0">
<soap:body use="literal" />
</wsdl:input>
- <wsdl:output name="getUserRoles_output0">
<soap:body use="literal" />
</wsdl:output>
- <wsdl:fault name="com.sap.security.api.UMException">
<soap:fault name="com.sap.security.api.UMException" use="literal" />
</wsdl:fault>
</wsdl:operation>
- <wsdl:operation name="getAllRolesInNameSpace">
<soap:operation soapAction="prt:service:com.sap.xcdr.xCDRServices.xCDRServices/getAllRolesInNameSpace0" />
- <wsdl:input name="getAllRolesInNameSpace_input0">
<soap:body use="literal" />
</wsdl:input>
- <wsdl:output name="getAllRolesInNameSpace_output0">
<soap:body use="literal" />
</wsdl:output>
- <wsdl:fault name="com.sap.security.api.UMException">
<soap:fault name="com.sap.security.api.UMException" use="literal" />
</wsdl:fault>
</wsdl:operation>
- <wsdl:operation name="assignRoles">
<soap:operation soapAction="prt:service:com.sap.xcdr.xCDRServices.xCDRServices/assignRoles0" />
- <wsdl:input name="assignRoles_input0">
<soap:body use="literal" />
</wsdl:input>
- <wsdl:output name="assignRoles_output0">
<soap:body use="literal" />
</wsdl:output>
- <wsdl:fault name="com.sap.security.api.UMException">
<soap:fault name="com.sap.security.api.UMException" use="literal" />
</wsdl:fault>
</wsdl:operation>
</wsdl:binding>
- <wsdl:service name="xCDRServicesService">
- <wsdl:port name="com.sap.portal.prt.soap.xCDRServices" binding="intf:com.sap.portal.prt.soap.xCDRServicesBinding">
<soap:address location="http://idesportaluss1.phl.sap.corp:1080/irj/servlet/prt/soap/com.sap.portal.prt.soap.xcdrservices?style=doc_lit" />
</wsdl:port>
</wsdl:service>
</wsdl:definitions>
Thanks very much in advance!
Regards,
Roman

By the way, I read a few post about this on SDN, but they didn't offer any solutions, and were from almost a year ago, so I was wondering if there's been any progress.

Client Proxy generation on a SAP NW 7.0 system using PI 7.1

Hello
Can anyone please guide me with Client Proxy generation on a SAP NW 7.0 system using PI 7.1 services with multiple operations. How does client proxy generation in SAP NW 7.00 support services with multiple operations ?
Thanks.
Kiran

Hi,
This could help you.
How to Activate Proxy.
How do you activate ABAP Proxies?
OutBound Proxy (Client Proxy)
Smarter Approach for coding ABAP Proxies
Outbound Proxy (Client Proxy)
ABAP Proxies in XI(Client Proxy)
Regards,
Sarvesh

Error in client proxy generation

Hi experts,
                I am trying to consume a web-service from an ABAP progam, to do this I create an Enterprise Service Client Proxy. But creation of the proxy fails with the error message
"Incorrect value: Unknown Namespace http://schemas.xmlsoap.org/soap/encoding/ .
      For client confidentiality issues I cannot put the wsdl file or its content on the thread but I can provide certain details of the code which you might wish to see.
Also my wsdl contains messages with miltiple parts.Is this also a trouble while generating the proxies in ABAP ?
Are these two problems related?
Can I find a link precisely which can provide a kind of checklist to see that these steps have to be followed or these conditions have to be met by wsdl for generation of client proxies in ABAP?
Any pointers will be useful.
Thanks and Regds
Abhishek

Hi Anton,
              I will provide you some piece of the file which might help you in analysing the problem....
<wsdl:definitions xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:tm="http://microsoft.com/wsdl/mime/textMatching/" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/"
xmlns:tns="http://www.abc.com"
xmlns:s1="http://www.abc.com/AbstractTypes"
xmlns:s="http://www.w3.org/2001/XMLSchema" xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/" xmlns:http="http://schemas.xmlsoap.org/wsdl/http/"
targetNamespace="http://www.abc.com"
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/">
    <s:schema targetNamespace="http://www.abc.com/AbstractTypes">
      <s:import namespace="http://schemas.xmlsoap.org/soap/encoding/" />
      <s:complexType name="StringArray">
        <s:complexContent mixed="false">
          <s:restriction base="soapenc:Array">
            <s:sequence>
              <s:element minOccurs="0" maxOccurs="unbounded" name="String" type="s:string" />
            </s:sequence>
          </s:restriction>
        </s:complexContent>
      </s:complexType>
    </s:schema>
Similarly the WSDL has messages with multiple parts like:
<wsdl:message name="GetReleasedGenericDrawing2DHttpGetIn">
    <wsdl:part name="DocumentNo" type="s:string" />
    <wsdl:part name="SheetNo" type="s:string" />
    <wsdl:part name="ClassName" type="s:string" />
</wsdl:message>
If you need some ther details from the file please let me know. I have cross checked that it is using a Document/literal style so it should not be a problem.
I have gone through the SAP note (944029) for the list some forbidden keywords which were a problem prior to release of SP 16 .We dont have even that problem.
This thing is very new to me ....please let me know if you wnat some other detail for analysis.
Regads
Abhishek

Client proxy generation in NWDS with external web service

Hello,
- I try to generate a client proxy in NWDS (7.0 SP12) from a wsdl which includes a complexType and which is non-SAP.
Wizard Procedure in NWDS: New client proxy definition > i select WSLD source = URL (it is same symptom with local file) > Then i fill URL > Proxy definition window: i see URI and package filled with value of complexType in wsdl file.
When i click on Finish, wizard generates some file on OS but there is error pop-up "Problems while generating the Proxy Definition".
NB.
Same procedure with a similar wsdl without complexType works well .
Objective is to use this proxy at SAP portal level.
- Main errors in NWDS logs:
Caused by: java.lang.Exception: WSDL part points to unavailable type with qname:
so, does anyone has encoutner this issue ? and also does complex type is supported ?!
(Notes that wsdl format is correct and if i remove "wsdl:type" portion and references, client proxy is correctly
created in NWDS.)
Thanks for help! Regards, Frédéric

Hi,
Complex types are supported but I am not sure if complextype with sequence is supported. See note: Incorrect field sequence with group SAP Note Number: 813545 (not sure if it is applicable to you as you are on NWSD 7.0 SP12).
Another note: SAP Note Number: 1266761
I suggest try to remove "sequence" and then try again.
Regards,
Gourav

Proxy generation Problem in Production system

Hi Experts,
I have consumed WSDL file and created Client Proxy in development system.which is working fine
After testing it is Transported to the Quality system and Production system both.
In Quality system Proxy is generated properly and functioning properly.
But in Production system, Proxy is not generated and even in Tcode SE80 it is not displaying.
How to solve this problem?
Please suggest.
Thanks in advance.
Regards
Jagesh

Hello Experts,
After Transporting Request to Production systems, all Dictionary objects are also created but Only Proxy is not created(Not appearing in SE80 under the respective package name).
Please help me in this.
Regards
Jagesh

Need some help regarding Client Proxy generation and test via SOAMANAGER

Hello,
we are integrating a 3rd party Java client via webservices.
For that matter I generated a client proxy (consumer proxy) in se80 using the existing WSDL.
This worked fine.
The I wanted to create a logical port.
Since this is only possible in SOAMANAGER I tried it there.
Trying to do this automatically by the given WSDL file didn't work. The system dumps.
So, I tried the manual approach by entering the server name and path in the 'Transport settings' tab.
Now I wanted to test this.
Unfortunately the test function in se80 (Proxy->Test) doesn't show a positive result.
I always get an error
SOAP:1.023 SRT: Processing error in Internet Communication Framework: ("ICF Error when receiving the response:
ICM_HTTP_CONNECTION_FAILED")
So, I am kind of stuck here.
Do you guys have any idea what's wrong (approach, settings, bugs)?.
I tested the webservices with a test application (soapUI), and they work fine.
So it seems to be a problem in the proxy framework or a network problem?
I really appreciate any kind of help.
Thanks,
Michael

i created the port in soamanager.Do i need to create in lpconfig also?
yes i have loaded the certificate in strust.
i am getting the response also from the web service. as Security requirements are not satisfied because the security header is not present in the incoming message.
i need to pass the user name and password while using the method.wsse security.wld u have any clue?

Advice on client proxy generation (ABAP and SAP PI)

Hi,
I've set up an ABAP client proxy using the wizard in transaction SE80 in the backend system, released it using transaction SOAMANAGER and tested that it works.
I now want to compare this technical approach against the same scenario using a proxy generated from a SAP PI outbound synchronous message interface.
I have hit the following issues:
1) When I upload the WSDL file (saved from the test web service I exposed from one of our SAP systems) into the Integration Repository, I receive the following error:
"Check Result for Object GetDOB_WSDL Document check found errors Cause: Unable to recognize the loaded document as valid WSDL Tag Policy is not permitted at position portType".
I can remove this error by deleting the tag policy but don't have an answer why this is not supported and whether this is the right approach - this error occurs regardless of which option I choose when saving the WSDL (i.e. portType or binding) or which upload option I select.
2) When I create the proxy in the backend system based on the message interface the objects are all created successfully and generate/activate correctly. As I don't need the PI runtime (no mapping, queuing etc) I go to create the logical port in transaction SOAMANAGER and I receive the error:
SRT Framework exception: The WSDL document is not compatible with proxy class "ZPROXCO_ZFUNC_UPDATE_ADDRESSHI": "Operation(s) Missing ZFuncUpdateAddresshistory"
even though the external operation does exist and is called ZFuncUpdateAddresshistory.
I have no clues as to why this doesn't work other than the generated WSDL file in the ABAP client proxy has the same name for the portType and operation (ZFuncUpdateAddresshistory).
3) Can someone please explain the value at design time over creating the client proxy in SAP PI versus using simply the wizard in the backend ABAP system - is it simply that the interfaces can be held centrally in the IR if desired or the WSDL might already be there and could be used to quickly generate a message interface?
Thanks,
Alan

Hi,
As far as I know, we follow the top down approach in proxy scenarios.
meaning, we first create the interfaces in XI IR and then go to the back end to implement them.
So, you should create a message interface (Probably Manually rather than importing the wsdl from R/3)
in IR and then go to the ERP backend to implement the proxy using the SPROXY transaction.
Coming to your 3rd question, In PI 7.1 you might be knowung that we have something called ESR(Enterprise Service Repository), which has all the services in a single place.This gives us an option of collating all the different enterprise services scattered all over different systems to be in a common repository.
Regards,
Ravi Kanth Talagana

Web Service - Client Proxy generation error

Hi All,
I tried creating a client proxy using an URL provided to me and followed the steps using the wizard. I end up in getting the following error messages. Could anyone throw some light on resolving this? I do not have any idea about what WSDL is. Any help is highly appreciated. Not able to attach the WSDL code here.
Below is the error message upon client proxy creation:
Proxy-Generierung: Fehler aufgetreten
Exception occurred in library handler
Not implemented
Thanks
Srini
Edited by: Srinivasan Karunakaran on Oct 22, 2010 11:11 PM

Resolved through SAP Help. Refer SAP note# 0001403271.

Proxy Generation Problem with Separate WSDL

Hi,
I'm trying to create Proxy with seperate WSDL, then i'm getting error. It is a simple Hello world BPEL and OSB.
Here is my WSDL
<?xml version="1.0" encoding="UTF-8" ?>
<definitions targetNamespace="http://www.uk.gov.hmrc.chiefste.org/hello"
xmlns="http://schemas.xmlsoap.org/wsdl/"
xmlns:tns="http://www.uk.gov.hmrc.chiefste.org/hello"
xmlns:imp1="http://xmlns.oracle.com/HelloWorld"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/"
xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/">
<types>
<xsd:schema targetNamespace="http://www.uk.gov.hmrc.chiefste.org/hello/types"
elementFormDefault="qualified">
<xsd:import schemaLocation="Hello.xsd"
namespace="http://xmlns.oracle.com/HelloWorld" id="hello.xsd"/>
</xsd:schema>
</types>
<message name="helloRequest">
<part name="inputParam" element="imp1:process"/>
</message>
<message name="helloResponse">
<part name="outputParam" element="imp1:processResponse"/>
</message>
<portType name="HelloService">
<operation name="sayHello">
<input message="tns:helloRequest"/>
<output message="tns:helloResponse"/>
</operation>
</portType>
<binding name="HelloServicePortBinding"
type="tns:HelloService">
<soap:binding style="document"
transport="http://schemas.xmlsoap.org/soap/http"/>
<operation name="sayHello">
<soap:operation style="document"
soapAction="http://www.uk.gov.hmrc.chiefste.org/common/sayHello"/>
<input>
<soap:body use="literal" parts="inputParam"/>
</input>
<output>
<soap:body use="literal" parts="outputParam"/>
</output>
</operation>
</binding>
<service name="HelloService">
<port name="HelloServicePort"
binding="tns:HelloServicePortBinding">
<soap12:address location="temp"/>
</port>
</service>
</definitions>
And here is my xsd
<?xml version="1.0" encoding="UTF-8"?>
<schema attributeFormDefault="unqualified"
          elementFormDefault="qualified"
          targetNamespace="http://xmlns.oracle.com/HelloWorld"
          xmlns="http://www.w3.org/2001/XMLSchema">
     <element name="process">
          <complexType>
               <sequence>
                    <element name="input" type="string"/>
               </sequence>
          </complexType>
     </element>
     <element name="processResponse">
          <complexType>
               <sequence>
                    <element name="result" type="string"/>
               </sequence>
          </complexType>
     </element>
</schema>
This is the WSDL i used to create a proxy service.
And this is the WSDL i used to generate Business Service (Which i got from my BPEL)
<?xml version="1.0" encoding="UTF-8" ?>
- <wsdl:definitions name="HelloWorld" targetNamespace="http://xmlns.oracle.com/CHIEF_STE_jws/TestProjectForOSB/HelloWorld" xmlns:plnk="http://schemas.xmlsoap.org/ws/2003/05/partner-link/" xmlns:client="http://xmlns.oracle.com/CHIEF_STE_jws/TestProjectForOSB/HelloWorld" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/">
- <wsdl:documentation>
<abstractWSDL>http://chfbpm1.acentres.capgemini.co.uk:8001/soa-infra/services/default/TestProjectForOSB!1.0/HelloWorld.wsdl</abstractWSDL>
</wsdl:documentation>
- <plnk:partnerLinkType name="HelloWorld">
- <plnk:role name="HelloWorldProvider">
<plnk:portType name="client:HelloWorld" />
</plnk:role>
</plnk:partnerLinkType>
- <wsdl:types>
- <schema xmlns="http://www.w3.org/2001/XMLSchema">
<import namespace="http://xmlns.oracle.com/CHIEF_STE_jws/TestProjectForOSB/HelloWorld" schemaLocation="http://chfbpm1.acentres.capgemini.co.uk:8001/soa-infra/services/default/TestProjectForOSB/helloworld_client_ep?XSD=xsd/HelloWorld.xsd" />
</schema>
</wsdl:types>
- <wsdl:message name="HelloWorldRequestMessage">
<wsdl:part name="payload" element="client:process" />
</wsdl:message>
- <wsdl:message name="HelloWorldResponseMessage">
<wsdl:part name="payload" element="client:processResponse" />
</wsdl:message>
- <wsdl:portType name="HelloWorld">
- <wsdl:operation name="process">
<wsdl:input message="client:HelloWorldRequestMessage" />
<wsdl:output message="client:HelloWorldResponseMessage" />
</wsdl:operation>
</wsdl:portType>
- <wsdl:binding name="HelloWorldBinding" type="client:HelloWorld">
<soap:binding xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" transport="http://schemas.xmlsoap.org/soap/http" />
- <wsdl:operation name="process">
<soap:operation xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" style="document" soapAction="process" />
- <wsdl:input>
<soap:body xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" use="literal" namespace="http://xmlns.oracle.com/CHIEF_STE_jws/TestProjectForOSB/HelloWorld" />
</wsdl:input>
- <wsdl:output>
<soap:body xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" use="literal" namespace="http://xmlns.oracle.com/CHIEF_STE_jws/TestProjectForOSB/HelloWorld" />
</wsdl:output>
</wsdl:operation>
</wsdl:binding>
- <wsdl:service name="helloworld_client_ep">
- <wsdl:port name="HelloWorld_pt" binding="client:HelloWorldBinding">
<soap:address xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" location="http://chfbpm1.acentres.capgemini.co.uk:8001/soa-infra/services/default/TestProjectForOSB/helloworld_client_ep" />
</wsdl:port>
</wsdl:service>
</wsdl:definitions>
Thx,
Rahul

Yes, U r rite. It takes input like that in SoapUI.
And in OSB Console it takes like below:
<soap:Header xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
</soap:Header>
<hel:process xmlns:hel="*http://xmlns.oracle.com/HelloWorld*">
<hel:input>?</hel:input>
</hel:process>
And this is my Input for Business Service in OSB Console:
<soap:Header xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
</soap:Header>
<hel:process xmlns:hel="*http://xmlns.oracle.com/CHIEF_STE_jws/TestProjectForOSB/HelloWorld*">
<hel:input>?</hel:input>
</hel:process>
Note: And if i use the Bolded namespace of Business Service in Proxy,, it is working.
This is my Request XQuery:
(:: pragma bea:global-element-parameter parameter="$process1" element="ns1:process" location="../Proxy/wsdl/Hello.xsd" ::)
(:: pragma bea:global-element-return element="ns0:process" location="../Business/wsdl/XMLSchema_1137514867.xsd" ::)
declare namespace ns1 = "http://xmlns.oracle.com/HelloWorld";
declare namespace ns0 = "http://xmlns.oracle.com/CHIEF_STE_jws/TestProjectForOSB/HelloWorld";
declare namespace xf = "http://tempuri.org/Hello/xquery/dsha/";
declare function xf:dsha($process1 as element(ns1:process))
as element(ns0:process) {
<ns0:process>
<ns0:input>{ data($process1/ns1:input) }</ns0:input>
</ns0:process>
declare variable $process1 as element(ns1:process) external;
xf:dsha($process1)
Response XQuery:
(:: pragma bea:global-element-parameter parameter="$processResponse1" element="ns0:processResponse" location="../Business/wsdl/XMLSchema_1137514867.xsd" ::)
(:: pragma bea:global-element-return element="ns1:processResponse" location="../Proxy/wsdl/Hello.xsd" ::)
declare namespace ns1 = "http://xmlns.oracle.com/HelloWorld";
declare namespace ns0 = "http://xmlns.oracle.com/CHIEF_STE_jws/TestProjectForOSB/HelloWorld";
declare namespace xf = "http://tempuri.org/Hello/xquery/resp/";
declare function xf:resp($processResponse1 as element(ns0:processResponse))
as element(ns1:processResponse) {
<ns1:processResponse>
<ns1:result>{ data($processResponse1/ns0:result) }</ns1:result>
</ns1:processResponse>
declare variable $processResponse1 as element(ns0:processResponse) external;
xf:resp($processResponse1)
Thx,
Rahul

NW 2004s ABAP - bugs in WS Client Proxy generation?

Hi!
I came across situation like this:
I exposed a web-service from the Sybase SQL Anywhere database (piece of cake - by the way!) and tried to consume this service from NW2004s ABAP. I have got almost a proper result like this:
The return parameter was an internal table LS_OUT-SOAPRESULT-ROWSET-ROW (I'll call it ROW further in the text). It had the correct number of rows, but only one field: a table-field called CONTROLLER, containing nothing. There were no values which correspond to the columns of the database table.
However, I could saw in a tunneling program that the SOAP message was correct - the values were there!
Then I consumed the same service from Java (just Java, not SAP NWAS Java) and got a correct result: the Row object was an array with correct number of members (the same as number of rows in SAP's ROW), but as opposed to ROW, it also contained the needed values in an object array called SOAPElement.
My guess is that SAP's Proxy generator "forgot" to include field(s) in the structure of the ROW internal table. I can only guess that there should be a table-field called SOAP_ELEMENT or similar.
Did something like this happen to anyone else? Is there something better to do except to program the service call manually?
Please share experience.
Thanks and regards,
Igor

Hi, Wolfgang!
Sorry for late reply - I wasn't dealing with the subject for a long time.
Even if there's no solution, nice to hear that I am not the only one experiencing the problem. It doesn't work. I can delete and generate the proxy over and over with the same result.
Did delete/create work for you?
The only option that I see left is to compose SOAP request manually and then parse the response by using transformations. This way I don't take the advantage of the new technology - I stay at the 620 level. But what can I do? The new fancy stuff simply doesn't work.
Igor

Web Service Proxy Generation failed

Hi @all,
i would like to consume a web service with the adaptive webdynpro model, but the proxy generation fails. Attached you will find the log file of the NWDS:
com.sap.tc.webdynpro.model.webservice.exception.WSModelRuntimeException: Exception on creation of service metadata for WSDL URL 'http://ktkrs3580/Elan2Webservice/elan_service.asmx?WSDL' and service factory configuration '{DynamicProxy.ClassPath=D:/Programme/SAP/IDE/IDE70/eclipse/plugins/com.sap.tc.cmi_1.0.0/_cmi_api.jar;D:/Programme/SAP/IDE/IDE70/eclipse/plugins/com.sap.exception_2.0.0/lib/exception.jar;D:/Programme/SAP/IDE/IDE70/eclipse/plugins/com.sap.engine.webservices_2.0.0/lib/boot.jar;D:/Programme/SAP/IDE/IDE70/eclipse/plugins/com.sap.engine.webservices_2.0.0/lib/iq-lib.jar;D:/Programme/SAP/IDE/IDE70/eclipse/plugins/com.sap.engine.webservices_2.0.0/lib/util.jar;D:/Programme/SAP/IDE/IDE70/eclipse/plugins/com.sap.engine.webservices_2.0.0/lib/webservices_lib.jar;D:/Programme/SAP/IDE/IDE70/eclipse/plugins/com.sap.engine.webservices_2.0.0/lib/webservices.jar;D:/Programme/SAP/IDE/IDE70/eclipse/plugins/com.sap.engine.webservices_2.0.0/lib/webservices_api.jar;D:/Programme/SAP/IDE/IDE70/eclipse/plugins/com.sap.engine.webservices_2.0.0/lib/tc_sec_wssec_lib.jar;D:/Programme/SAP/IDE/IDE70/eclipse/plugins/com.sap.dictionary.runtime_2.0.0/lib/SapDictionaryTypesRuntime.jar;D:/Programme/SAP/IDE/IDE70/eclipse/plugins/com.sap.dictionary.services_2.0.0/lib/SapDictionaryTypeServices.jar;D:/Programme/SAP/IDE/IDE70/eclipse/plugins/com.tssap.sap.libs.logging_2.0.0/lib/logging.jar;D:/Programme/SAP/IDE/IDE70/eclipse/plugins/com.tssap.sap.libs.logging_2.0.0/lib/loggingStandard.jar;D:/Programme/SAP/IDE/IDE70/eclipse/plugins/com.tssap.sap.libs.logging_2.0.0/lib/jARM.jar;D:/Programme/SAP/IDE/IDE70/eclipse/plugins/com.tssap.sap.libs.xmltoolkit_2.0.0/lib/sapxmltoolkit.jar;D:/Programme/SAP/IDE/IDE70/eclipse/plugins/com.sap.ext.libs.webservices_2.0.0/lib/activation.jar;D:/Programme/SAP/IDE/IDE70/eclipse/plugins/com.sap.ext.libs.webservices_2.0.0/lib/jaxm-api.jar;D:/Programme/SAP/IDE/IDE70/eclipse/plugins/com.sap.ext.libs.webservices_2.0.0/lib/saaj-api.jar;D:/Programme/SAP/IDE/IDE70/eclipse/plugins/com.sap.ext.libs.webservices_2.0.0/lib/jaxrpc-api.jar;D:/Programme/SAP/IDE/IDE70/eclipse/plugins/com.sap.ext.libs.webservices_2.0.0/lib/jnet.jar;D:/Programme/SAP/IDE/IDE70/eclipse/plugins/com.sap.ext.libs.webservices_2.0.0/lib/jsse.jar;D:/Programme/SAP/IDE/IDE70/eclipse/plugins/com.sap.ext.libs.webservices_2.0.0/lib/mail.jar;D:/Programme/SAP/IDE/IDE70/eclipse/plugins/com.sap.tc.webdynpro.model.webservice_2.0.0/lib/_webdynpro_model_webservice.jar;, DynamicProxy.INetProxy.Bypass=, DynamicProxy.INetProxy.Port=8080, DynamicProxy.Javac.path=C:\j2sdk1.4.2_12, DynamicProxy.TempDir=C:\DOKUME1\branch\LOKALE1\Temp\, DynamicProxy.INetProxy.Host=tknproxy}'
at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.getOrCreateWsrService(WSModelInfo.java:414)
at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.readOperationsFromWSDL(WSModelInfo.java:372)
at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.importMetadataInternal(WSModelInfo.java:342)
at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.importMetadata(WSModelInfo.java:306)
at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.importMetadata(WSModelInfo.java:316)
at com.sap.ide.webdynpro.modeleditor.wizards.model.creation.PageRenameWS.loadNameSpacesAndModelClasses(PageRenameWS.java:435)
at com.sap.ide.webdynpro.modeleditor.wizards.model.creation.ModelDialog.nextPressed(ModelDialog.java:105)
at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:316)
at org.eclipse.jface.dialogs.Dialog$1.widgetSelected(Dialog.java:423)
at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:89)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:81)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:840)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:2022)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:1729)
at org.eclipse.jface.window.Window.runEventLoop(Window.java:583)
at org.eclipse.jface.window.Window.open(Window.java:563)
at com.sap.ide.webdynpro.modeleditor.ModelEditorCallback.createModel(ModelEditorCallback.java:52)
at com.sap.ide.webdynpro.service.modeleditor.ModelService.createModelWithUI(ModelService.java:70)
at com.sap.ide.webdynpro.service.modeleditor.ServiceWithUI.createModel(ServiceWithUI.java:49)
at com.sap.ide.webdynpro.tsmodel.application.provider.ModelNodeProvider.createUniqueName(ModelNodeProvider.java:55)
at com.tssap.selena.impl.model.elements.EntityImpl.createChildEntityUin(EntityImpl.java:936)
at com.tssap.selena.impl.model.elements.EntityImpl.createChildEntity(EntityImpl.java:502)
at com.sap.ide.webdynpro.tsmodel.application.actions.CreationAction.runInternal(CreationAction.java:76)
at com.sap.ide.webdynpro.tsmodel.application.actions.CreationAction.access$000(CreationAction.java:24)
at com.sap.ide.webdynpro.tsmodel.application.actions.CreationAction$1.run(CreationAction.java:51)
at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1595)
at com.sap.ide.webdynpro.tsmodel.application.actions.CreationAction.run(CreationAction.java:57)
at com.sap.ide.webdynpro.projectbrowser.actions.PBCreateModelAction.run(PBCreateModelAction.java:95)
at com.tssap.selena.model.extension.action.SelenaActionCollector$GenericElementActionWrapper.run(SelenaActionCollector.java:224)
at com.tssap.util.ui.menu.MenuFactory$MuSiAction.saveRunAction(MenuFactory.java:1425)
at com.tssap.util.ui.menu.MenuFactory$MuSiAction.run(MenuFactory.java:1407)
at com.tssap.util.ui.menu.MenuFactory$DelegateAction.processInternal(MenuFactory.java:616)
at com.tssap.util.ui.menu.MenuFactory$DelegateAction.access$100(MenuFactory.java:586)
at com.tssap.util.ui.menu.MenuFactory$DelegateAction$BusyProcessWorker.run(MenuFactory.java:716)
at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:69)
at com.tssap.util.ui.menu.MenuFactory$DelegateAction.process(MenuFactory.java:610)
at com.tssap.util.ui.menu.internal.MenuListenerFactory$ProcessAdapter.widgetSelected(MenuListenerFactory.java:172)
at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:89)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:81)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:840)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:2022)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:1729)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1402)
at org.eclipse.ui.internal.Workbench.run(Workbench.java:1385)
at com.tssap.util.startup.WBLauncher.run(WBLauncher.java:79)
at org.eclipse.core.internal.boot.InternalBootLoader.run(InternalBootLoader.java:858)
at org.eclipse.core.boot.BootLoader.run(BootLoader.java:461)
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:324)
at com.sap.ide.eclipse.startup.Main.basicRun(Main.java:291)
at com.sap.ide.eclipse.startup.Main.run(Main.java:789)
at com.sap.ide.eclipse.startup.Main.main(Main.java:607)
Caused by: com.sap.engine.services.webservices.jaxrpc.exceptions.WebserviceClientException: GenericServiceFactory initialization problem. Could not load web service model. See nested exception for details.
at com.sap.engine.services.webservices.espbase.client.dynamic.impl.DGenericServiceImpl.generateProxyFiles(DGenericServiceImpl.java:150)
at com.sap.engine.services.webservices.espbase.client.dynamic.impl.DGenericServiceImpl.<init>(DGenericServiceImpl.java:50)
at com.sap.engine.services.webservices.espbase.client.dynamic.GenericServiceFactory.createService(GenericServiceFactory.java:88)
at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.getOrCreateWsrService(WSModelInfo.java:412)
... 53 more
Caused by: com.sap.engine.services.webservices.jaxrpc.exceptions.ProxyGeneratorException: Proxy Generator Error. Proxy generation problem. See nested exception.
at com.sap.engine.services.webservices.jaxrpc.wsdl2java.ProxyGenerator.generateProxy(ProxyGenerator.java:283)
at com.sap.engine.services.webservices.espbase.client.dynamic.impl.DGenericServiceImpl.generateProxyFiles(DGenericServiceImpl.java:147)
... 56 more
Caused by: java.io.IOException: Compilation fails...
C:\Dokumente und Einstellungen\branch\Lokale Einstellungen\Temp\DGenService1207743399620\types\p1\RelationCIShort.java:161: getIdCI() is already defined in types.p1.RelationCIShort
public java.lang.Integer getIdCI() {
^
C:\Dokumente und Einstellungen\branch\Lokale Einstellungen\Temp\DGenService1207743399620\types\p1\RelationCIShort.java:164: hasIdCI() is already defined in types.p1.RelationCIShort
public boolean hasIdCI() {
^
2 errors
THX!
Regards,
Christian

found the fix discussed on this blog... http://kingsfleet.blogspot.com/2008/07/working-round-xsdchoice-binding-issue.html

ABAP client proxy create error

Hi,
When I try to create a client proxy web service (se80), I get the error "Error when creating HTTP client: URL: Error:Connection Parameters (Host or Service) Not Availa Message no. SPRX137"
I want to consume a web service (by reading a wsdl from an url) from my own network. the ICM seems to work fine.
Any ideas?
thanks,
Raymond Does

Hi Praveen,
Actualy I am not using XI. I would like to connect to the web service by creating a client proxy and then calling the web service with an ABAP program.
I that case, do I have to do the SPROXY settings as well?
While debugging the creation of the client proxy I saw that the urls to the wsdl and xsd files (my wsdl is refering to them) did not have the complete http://..etc.. text but only the last part (like 'SystemGetInfo.wsdl'). It seems that the client proxy generation program cannot handle this url data.
Please let me know what to do.
Regards,
Raymond

Problems in ABAP Proxy Generation

Hi All,
I tried to generate an ABAP proxy for outbound message interface "Interface_ABC", which is under software component "DEF".
In our development system, I had successfully created ordinary function modules and structures under the package "/XYZ/UVW" using the prefix "/XYZ/".
When I began the proxy generation, the system asked me to specify the package and prefix. So I specified the package to be "/XYZ/UVW" and prefix to be "/XYZ/".
Then a warning window pops up. It reads "Package /XYZ/UVW does not belong to DEF". I clicked "OK". The "Create Proxy" screen shows up. Then I clicked the "Save" button. This time an error window pops up. It reads "Cannot extend package /XYZ/UVW". The action is thus cancelled by the system.
Does anybody know what is the reason for this problem and how to solve it?
Best Regards
Jerome

Please check the properties of the package in which you are tyring to save the PROXY.
In your case it looks like the property PACKAGE NOT EXTENDABLE is switched on. Once you uncheck you should be able to save the proxy in that package.
Regards,
Ravi
Note : Please reward points if you find the answer useful.

Client proxy generation problem

Similar Messages

Maybe you are looking for