SOAP Adapterd --importing wsdl file

hi
I am doing the following scenario, in page no 6, where do I get GoogleSearch.wsdl to import ?
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/d23cbe11-0d01-0010-5287-873a22024f79

Hi,
istead of copy the file from browser, you can get the valid file from the below link
http://www.phpclasses.org/browse/file/6180.html, it is free , plz subscribe and download.
also
http://code.google.com/apis/soapsearch/api_faq.html -- valid
also
www.onlamp.com/security/2004/10/07/examples/GoogleSearch.wsdl
api.google.com/GoogleSearch.wsdl
www.soapclient.com/xml/googleSearch.wsdl
Regards
Chilla

Similar Messages

Error while Importing Wsdl file of of 189 KB to XI Server.

Hi,
I am working on SAP NW 7.0.This is the Error I am getting while importing wsdl file of 189 KB to XI server.
Error :
Connection Interrupted.
Connection to server lost.
You can log on again once the server is available again.
Do you want to log on again.
Asking for password.
Another WSDL file of 8 KB successfully imported to XI server.
Please provide your reply on this asap.
Regards
Nilesh.

check this,
Note 1334387 - WSDL Import wizard fails with connection timeout exception
Regards,
Ravi

Import WSDL file along with XSD

Hi,
I have a WSDL file which has complex Data types (abc.wsdl). This complex data types are defined in the XSD file (abc-data.xsd).
If I just import WSDL file in ED I am unable to find the Complex Data types in Message Mapping.
How can I use the XSD file along with the WSDL file? Is there any source path as to give or what?
Could you please help me out?

first i will tell how my wsdl file is defined
<xs:element name="authInfo" type="<b>xx:AuthInfo</b>">                                   <xs:annotation>                              <xs:documentation xml:lang="en">                                   Authentication information                         </xs:documentation>                    </xs:annotation>                              </xs:element>
and in my xsd file for xx:AuthInfo
<xs:complexType name="AuthInfo">
          <xs:sequence>
               <xs:element name="acctName" type="tns:CustName">
                    <xs:annotation>
                         <xs:documentation xml:lang="en">
                         account name.
                    </xs:documentation>
                    </xs:annotation>
               </xs:element>
               <xs:element name="password" type="tns:AcctPswd">
                    <xs:annotation>
                         <xs:documentation xml:lang="en">
                        Specify the password                    </xs:documentation>
                    </xs:annotation>
               </xs:element>
          </xs:sequence>
     </xs:complexType>
when i import wsdl file in Ed i will get two inputs there but only one as "AuthInfo"
but "AuthInfo" has two inputs.
this is how my Target Message Look like
Tree          Occurences          Type
authInfo     1..1                      xx:AuthInfo
i hope i have cleared u..

Messages not adviced in extern definition after import wsdl-file from WAS

Hi friends,
after importing the three wsld-files in repository (extern definitions) the messages are not adviced. The referendes to the files are fine, because the name is shown at the tab externe...
But i´m not shure wheather i tool the right link ant Web Service Navigator. It is right to download the default SAP WSDL Files or the default one? Because in the SAP WSDL-files there will be an exception during import in XI repository (tag sap:useFeatur). What is the problem that the messages are not shown on the tab messages in externe definitions?
Thanks in advance,
Frank

I've the same problem. Here is my WSDL:
<?xml version="1.0" encoding="UTF-8"?>
<wsdl:definitions targetNamespace="http://blablabla.de:8080/jboss-net/services/MyServices" xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:apachesoap="http://xml.apache.org/xml-soap" xmlns:impl="http://blablabla.de:8080/jboss-net/services/MyServices" xmlns:intf="http://blablabla.de:8080/jboss-net/services/MyServices" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:tns1="blablabla.de" xmlns:tns2="http://net.jboss.org/jmx" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
     <wsdl:types>
          <schema targetNamespace="blablabla.de" xmlns="http://www.w3.org/2001/XMLSchema">
               <import namespace="http://schemas.xmlsoap.org/soap/encoding/"/>
               <complexType name="MSOBean">
                    <sequence>
                         <element name="installationName" nillable="true" type="xsd:string"/>
                         <element name="requestId" nillable="true" type="xsd:string"/>
                         <element name="returnCode" type="xsd:int"/>
                         <element name="returnMessage" nillable="true" type="xsd:string"/>
                    </sequence>
               </complexType>
               <complexType name="MSIBean">
                    <sequence>
                         <element name="password" nillable="true" type="xsd:string"/>
                         <element name="project" nillable="true" type="xsd:string"/>
                         <element name="requestId" nillable="true" type="xsd:string"/>
                         <element name="userId" nillable="true" type="xsd:string"/>
                    </sequence>
               </complexType>
          </schema>
     </wsdl:types>
     <wsdl:message name="actualizeRequest">
          <wsdl:part name="inData" type="tns1:MSIBean"/>
     </wsdl:message>
     <wsdl:message name="actualizeResponse">
          <wsdl:part name="actualizeReturn" type="tns1:MSOBean"/>
     </wsdl:message>
     <wsdl:portType name="MSService">
          <wsdl:operation name="actualize" parameterOrder="inData">
               <wsdl:input message="impl:actualizeRequest" name="actualizeRequest"/>
               <wsdl:output message="impl:actualizeResponse" name="actualizeResponse"/>
          </wsdl:operation>
     </wsdl:portType>
     <wsdl:binding name="MyServicesSoapBinding" type="impl:MSService">
          <wsdlsoap:binding style="rpc" transport="http://schemas.xmlsoap.org/soap/http"/>
          <wsdl:operation name="actualize">
               <wsdlsoap:operation soapAction=""/>
               <wsdl:input name="actualizeRequest">
                    <wsdlsoap:body encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="http://blablabla.de" use="encoded"/>
               </wsdl:input>
               <wsdl:output name="actualizeResponse">
                    <wsdlsoap:body encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="http://blablabla.de:8080/jboss-net/services/MyServices" use="encoded"/>
               </wsdl:output>
          </wsdl:operation>
     </wsdl:binding>
     <wsdl:service name="MSServiceService">
          <wsdl:port binding="impl:MyServicesSoapBinding" name="MyServices">
               <wsdlsoap:address location="http://blablabla.de:8080/jboss-net/services/MyServices"/>
          </wsdl:port>
     </wsdl:service>
</wsdl:definitions>
No Idea.

Problem in Importing wsdl file in IR

Hi ,
I am doing soap receiver scenario.I had a wsdl generated from .Net and i imported the wsdl , i am not able to find teh methods in the external defination ,
Wat wil be theproblem.
Regards,
Shaik

Hi,
problems occur during the import of xsd and wsdl files as external definitions if the target namespace contains more than 60 characters. The system does not issue any error message, however, the list of the
recognized messages remains empty.
Solution;
For a wsdl file, you simply need to edit the target namespace manually ( attribute "targetNamespace" of the wsdl:definitions element) and reduce the number of characters to less than 60. For the structure of the extracted messages (exception: import assuming rpc style binding, see below), this target namespace does not have any importance.
Regards,
Jayasimha Jangam

Error importing WSDL file

Hi All,
When i try to import a WSDL file in the repository as an external definition i get the following error message:
"Unable to convert imported document to WSDL
Reason: Tag input cannot have an attribute message from namespace
Check the selected category"
Below here is the WSDL file. Can anyone see what i do wrong and/or is wrong with the WSDL file?
thanks a bunch!
Jeff
<?xml version="1.0" encoding="utf-8"?>
<definitions xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:xs="http://www.w3.org/2001/XMLSchema" name="IwsSAPPocservice"
targetNamespace="urn://test/" xmlns:tns="urn://test/" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/"
xmlns:ns1="urn:tpg_sapxi-wsSAPPocIntf">
<types>
    <xs:schema targetNamespace="urn:tpg_sapxi-wsSAPPocIntf" xmlns="urn:tpg_sapxi-wsSAPPocIntf">
      <xs:complexType name="TRemotableOrder">
        <xs:sequence>
          <xs:element name="DagID" type="xs:int"/>
          <xs:element name="OrderNr" type="xs:int"/>
          <xs:element name="BedrLoc_Proc_Cd" type="xs:int"/>
          <xs:element name="KlantNr" type="xs:int"/>
          <xs:element name="KlantNr_Verreken" type="xs:int"/>
          <xs:element name="Aanpak_Loc_Cd" type="xs:int"/>
          <xs:element name="Aanpak_OrderNr" type="xs:int"/>
          <xs:element name="Aanpak_Order_Dt" type="xs:dateTime"/>
          <xs:element name="OrderRegels" type="ns1:OrderRegelArray"/>
        </xs:sequence>
      </xs:complexType>
      <xs:complexType name="OrderRegelArray">
        <xs:complexContent>
          <xs:restriction base="soapenc:Array">
            <xs:sequence/>
            <xs:attribute ref="soapenc:arrayType" n1:arrayType="ns1:TRemotableOrderRegel[]"
xmlns:n1="http://schemas.xmlsoap.org/wsdl/"/>
          </xs:restriction>
        </xs:complexContent>
      </xs:complexType>
      <xs:complexType name="TRemotableOrderRegel">
        <xs:sequence>
          <xs:element name="OrderRegelNr" type="xs:int"/>
          <xs:element name="ProdAfsprNr" type="xs:int"/>
          <xs:element name="ProdSrt_ID" type="xs:int"/>
          <xs:element name="Landen_Groep" type="xs:int"/>
          <xs:element name="Frank_Wijze_OptieSrt_Cd" type="xs:int"/>
          <xs:element name="Ref_Aantal" type="xs:double"/>
          <xs:element name="MeetEh_Cd_Aantal" type="xs:int"/>
          <xs:element name="Ref_Gew" type="xs:double"/>
          <xs:element name="MeetEh_Cd_Ref_Aantal" type="xs:int"/>
          <xs:element name="Ptt_Aantal" type="xs:int"/>
          <xs:element name="Ptt_Gewicht_Per_Zending" type="xs:double"/>
          <xs:element name="Partij_Gewogen_Totaal" type="xs:double"/>
          <xs:element name="Partij_Handmatig" type="xs:double"/>
          <xs:element name="Metingen" type="ns1:OrderRegelMetingenArray"/>
          <xs:element name="ProdAfspraken" type="ns1:OrderRegelProdAfsprakenArray"/>
        </xs:sequence>
      </xs:complexType>
      <xs:complexType name="OrderRegelMetingenArray">
        <xs:complexContent>
          <xs:restriction base="soapenc:Array">
            <xs:sequence/>
            <xs:attribute ref="soapenc:arrayType" n1:arrayType="ns1:TRemotableOrderRegelMeting[]"
xmlns:n1="http://schemas.xmlsoap.org/wsdl/"/>
          </xs:restriction>
        </xs:complexContent>
      </xs:complexType>
      <xs:complexType name="OrderRegelProdAfsprakenArray">
        <xs:complexContent>
          <xs:restriction base="soapenc:Array">
            <xs:sequence/>
            <xs:attribute ref="soapenc:arrayType" n1:arrayType="ns1:TOrderRegelProdAfspraak[]"
xmlns:n1="http://schemas.xmlsoap.org/wsdl/"/>
          </xs:restriction>
        </xs:complexContent>
      </xs:complexType>
      <xs:complexType name="TRemotableOrderRegelMeting">
        <xs:sequence>
          <xs:element name="OptieSrt_Cd" type="xs:int"/>
          <xs:element name="MeetEenh_Cd" type="xs:int"/>
          <xs:element name="OrderRgl_Met_Wrd" type="xs:double"/>
        </xs:sequence>
      </xs:complexType>
      <xs:complexType name="TOrderRegelProdAfspraak">
        <xs:sequence>
          <xs:element name="ProdAfsprNr" type="xs:int"/>
          <xs:element name="Oordeel_Balie_Cd" type="xs:int"/>
          <xs:element name="Res_Ctr_Vnw_1" type="xs:int"/>
          <xs:element name="Res_Ctr_Vnw_2" type="xs:int"/>
          <xs:element name="Res_Ctr_Vnw_3" type="xs:int"/>
          <xs:element name="Ers_Afhandelingscode" type="xs:string"/>
          <xs:element name="Min_Aantal_Voorw_Ind" type="xs:string"/>
        </xs:sequence>
      </xs:complexType>
      <xs:complexType name="PrijsInfoArray">
        <xs:complexContent>
          <xs:restriction base="soapenc:Array">
            <xs:sequence/>
            <xs:attribute ref="soapenc:arrayType" n1:arrayType="ns1:TRemotablePrijsInfo[]"
xmlns:n1="http://schemas.xmlsoap.org/wsdl/"/>
          </xs:restriction>
        </xs:complexContent>
      </xs:complexType>
      <xs:complexType name="TRemotablePrijsInfo">
        <xs:sequence>
          <xs:element name="RegelNr" type="xs:int"/>
          <xs:element name="PrijsNr" type="xs:int"/>
          <xs:element name="Prijs" type="xs:double"/>
          <xs:element name="Btw" type="xs:double"/>
        </xs:sequence>
      </xs:complexType>
    </xs:schema>
</types>
<message name="prijsOrderRegel0Request">
    <part name="klantnr_verreken" type="xs:int"/>
    <part name="aanpak_loc_cd" type="xs:int"/>
    <part name="orderrglnr" type="xs:int"/>
    <part name="prodafsprnr" type="xs:int"/>
    <part name="prodsrt_id" type="xs:int"/>
    <part name="landen_groep" type="xs:int"/>
    <part name="frank_wijze_optiesrt_cd" type="xs:int"/>
    <part name="Prijs" type="xs:double"/>
    <part name="BTW" type="xs:double"/>
</message>
<message name="prijsOrderRegel0Response">
    <part name="Prijs" type="xs:double"/>
    <part name="BTW" type="xs:double"/>
    <part name="return" type="xs:int"/>
</message>
<message name="prijsOrderObj1Request">
    <part name="order" type="ns1:TRemotableOrder"/>
</message>
<message name="prijsOrderObj1Response">
    <part name="return" type="ns1:PrijsInfoArray"/>
</message>
<portType name="IwsSAPPoc">
    <operation name="prijsOrderRegel">
      <input message="tns:prijsOrderRegel0Request"/>
      <output message="tns:prijsOrderRegel0Response"/>
    </operation>
    <operation name="prijsOrderObj">
      <input message="tns:prijsOrderObj1Request"/>
      <output message="tns:prijsOrderObj1Response"/>
    </operation>
</portType>
<binding name="IwsSAPPocbinding" type="tns:IwsSAPPoc">
    <soap:binding style="rpc" transport="http://schemas.xmlsoap.org/soap/http"/>
    <operation name="prijsOrderRegel">
      <soap:operation soapAction="urn:tpg_sapxi-wsSAPPocIntf-IwsSAPPoc#prijsOrderRegel" style="rpc"/>
      <input message="tns:prijsOrderRegel0Request">
        <soap:body use="encoded" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"
namespace="urn:tpg_sapxi-wsSAPPocIntf-IwsSAPPoc"/>
      </input>
      <output message="tns:prijsOrderRegel0Response">
        <soap:body use="encoded" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"
namespace="urn:tpg_sapxi-wsSAPPocIntf-IwsSAPPoc"/>
      </output>
    </operation>
    <operation name="prijsOrderObj">
      <soap:operation soapAction="urn:tpg_sapxi-wsSAPPocIntf-IwsSAPPoc#prijsOrderObj" style="rpc"/>
      <input message="tns:prijsOrderObj1Request">
        <soap:body use="encoded" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"
namespace="urn:tpg_sapxi-wsSAPPocIntf-IwsSAPPoc"/>
      </input>
      <output message="tns:prijsOrderObj1Response">
        <soap:body use="encoded" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"
namespace="urn:tpg_sapxi-wsSAPPocIntf-IwsSAPPoc"/>
      </output>
    </operation>
</binding>
<service name="IwsSAPPocservice">
    <port name="IwsSAPPocPort" binding="tns:IwsSAPPocbinding">
      <soap:address location="http://prid0059.tpgpost.local/SAPPocWebService/SAPPocWebService.exe/soap/IwsSAPPoc"/>
    </port>
</service>
</definitions>

Hi Jeffrey,
Modify the file like this, it will work.
<?xml version="1.0" encoding="ISO-8859-1"?>
<definitions xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"<b> xmlns:tns="urn://test/"</b> xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:ns1="urn:tpg_sapxi-wsSAPPocIntf" xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" name="IwsSAPPocservice" targetNamespace="urn://test/">
     <types>
          <xs:schema xmlns="urn:tpg_sapxi-wsSAPPocIntf" targetNamespace="urn:tpg_sapxi-wsSAPPocIntf">
               <xs:complexType name="TRemotableOrder">
                    <xs:sequence>
                         <xs:element name="DagID" type="xs:int" />
                         <xs:element name="OrderNr" type="xs:int" />
                         <xs:element name="BedrLoc_Proc_Cd" type="xs:int" />
                         <xs:element name="KlantNr" type="xs:int" />
                         <xs:element name="KlantNr_Verreken" type="xs:int" />
                         <xs:element name="Aanpak_Loc_Cd" type="xs:int" />
                         <xs:element name="Aanpak_OrderNr" type="xs:int" />
                         <xs:element name="Aanpak_Order_Dt" type="xs:dateTime" />
                         <xs:element name="OrderRegels" type="ns1:OrderRegelArray" />
                    </xs:sequence>
               </xs:complexType>
               <xs:complexType name="OrderRegelArray">
                    <xs:complexContent>
                         <xs:restriction base="soapenc:Array">
                              <xs:sequence />
                              <xs:attribute xmlns:n1="http://schemas.xmlsoap.org/wsdl/" ref="soapenc:arrayType" n1:arrayType="ns1:TRemotableOrderRegel[]" />
                         </xs:restriction>
                    </xs:complexContent>
               </xs:complexType>
               <xs:complexType name="TRemotableOrderRegel">
                    <xs:sequence>
                         <xs:element name="OrderRegelNr" type="xs:int" />
                         <xs:element name="ProdAfsprNr" type="xs:int" />
                         <xs:element name="ProdSrt_ID" type="xs:int" />
                         <xs:element name="Landen_Groep" type="xs:int" />
                         <xs:element name="Frank_Wijze_OptieSrt_Cd" type="xs:int" />
                         <xs:element name="Ref_Aantal" type="xs:double" />
                         <xs:element name="MeetEh_Cd_Aantal" type="xs:int" />
                         <xs:element name="Ref_Gew" type="xs:double" />
                         <xs:element name="MeetEh_Cd_Ref_Aantal" type="xs:int" />
                         <xs:element name="Ptt_Aantal" type="xs:int" />
                         <xs:element name="Ptt_Gewicht_Per_Zending" type="xs:double" />
                         <xs:element name="Partij_Gewogen_Totaal" type="xs:double" />
                         <xs:element name="Partij_Handmatig" type="xs:double" />
                         <xs:element name="Metingen" type="ns1:OrderRegelMetingenArray" />
                         <xs:element name="ProdAfspraken" type="ns1:OrderRegelProdAfsprakenArray" />
                    </xs:sequence>
               </xs:complexType>
               <xs:complexType name="OrderRegelMetingenArray">
                    <xs:complexContent>
                         <xs:restriction base="soapenc:Array">
                              <xs:sequence />
                              <xs:attribute xmlns:n1="http://schemas.xmlsoap.org/wsdl/" ref="soapenc:arrayType" n1:arrayType="ns1:TRemotableOrderRegelMeting[]" />
                         </xs:restriction>
                    </xs:complexContent>
               </xs:complexType>
               <xs:complexType name="OrderRegelProdAfsprakenArray">
                    <xs:complexContent>
                         <xs:restriction base="soapenc:Array">
                              <xs:sequence />
                              <xs:attribute xmlns:n1="http://schemas.xmlsoap.org/wsdl/" ref="soapenc:arrayType" n1:arrayType="ns1:TOrderRegelProdAfspraak[]" />
                         </xs:restriction>
                    </xs:complexContent>
               </xs:complexType>
               <xs:complexType name="TRemotableOrderRegelMeting">
                    <xs:sequence>
                         <xs:element name="OptieSrt_Cd" type="xs:int" />
                         <xs:element name="MeetEenh_Cd" type="xs:int" />
                         <xs:element name="OrderRgl_Met_Wrd" type="xs:double" />
                    </xs:sequence>
               </xs:complexType>
               <xs:complexType name="TOrderRegelProdAfspraak">
                    <xs:sequence>
                         <xs:element name="ProdAfsprNr" type="xs:int" />
                         <xs:element name="Oordeel_Balie_Cd" type="xs:int" />
                         <xs:element name="Res_Ctr_Vnw_1" type="xs:int" />
                         <xs:element name="Res_Ctr_Vnw_2" type="xs:int" />
                         <xs:element name="Res_Ctr_Vnw_3" type="xs:int" />
                         <xs:element name="Ers_Afhandelingscode" type="xs:string" />
                         <xs:element name="Min_Aantal_Voorw_Ind" type="xs:string" />
                    </xs:sequence>
               </xs:complexType>
               <xs:complexType name="PrijsInfoArray">
                    <xs:complexContent>
                         <xs:restriction base="soapenc:Array">
                              <xs:sequence />
                              <xs:attribute xmlns:n1="http://schemas.xmlsoap.org/wsdl/" ref="soapenc:arrayType" n1:arrayType="ns1:TRemotablePrijsInfo[]" />
                         </xs:restriction>
                    </xs:complexContent>
               </xs:complexType>
               <xs:complexType name="TRemotablePrijsInfo">
                    <xs:sequence>
                         <xs:element name="RegelNr" type="xs:int" />
                         <xs:element name="PrijsNr" type="xs:int" />
                         <xs:element name="Prijs" type="xs:double" />
                         <xs:element name="Btw" type="xs:double" />
                    </xs:sequence>
               </xs:complexType>
          </xs:schema>
     </types>
     <message name="prijsOrderRegel0Request">
          <part name="klantnr_verreken" type="xs:int" />
          <part name="aanpak_loc_cd" type="xs:int" />
          <part name="orderrglnr" type="xs:int" />
          <part name="prodafsprnr" type="xs:int" />
          <part name="prodsrt_id" type="xs:int" />
          <part name="landen_groep" type="xs:int" />
          <part name="frank_wijze_optiesrt_cd" type="xs:int" />
          <part name="Prijs" type="xs:double" />
          <part name="BTW" type="xs:double" />
     </message>
     <message name="prijsOrderRegel0Response">
          <part name="Prijs" type="xs:double" />
          <part name="BTW" type="xs:double" />
          <part name="return" type="xs:int" />
     </message>
     <message name="prijsOrderObj1Request">
          <part name="order" type="ns1:TRemotableOrder" />
     </message>
     <message name="prijsOrderObj1Response">
          <part name="return" type="ns1:PrijsInfoArray" />
     </message>
     <portType name="IwsSAPPoc">
          <operation name="prijsOrderRegel">
<b>               <tns:input message="prijsOrderRegel0Request" />
               <tns:output message="prijsOrderRegel0Response" /></b>
          </operation>
          <operation name="prijsOrderObj">
<b>               <tns:input message="prijsOrderObj1Request" />
               <tns:output message="prijsOrderObj1Response" /></b>
          </operation>
     </portType>
     <binding name="IwsSAPPocbinding" type="tns:IwsSAPPoc">
          <soap:binding style="rpc" transport="http://schemas.xmlsoap.org/soap/http" />
          <operation name="prijsOrderRegel">
               <soap:operation soapAction="urn:tpg_sapxi-wsSAPPocIntf-IwsSAPPoc#prijsOrderRegel" style="rpc" />
<b>               <tns:input message="prijsOrderRegel0Request"></b>
                    <soap:body use="encoded" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="urn:tpg_sapxi-wsSAPPocIntf-IwsSAPPoc" />
<b>               </tns:input>
               <tns:output message="prijsOrderRegel0Response"></b>
                    <soap:body use="encoded" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="urn:tpg_sapxi-wsSAPPocIntf-IwsSAPPoc" />
               <b></tns:output></b>
          </operation>
          <operation name="prijsOrderObj">
               <soap:operation soapAction="urn:tpg_sapxi-wsSAPPocIntf-IwsSAPPoc#prijsOrderObj" style="rpc" />
<b>               <tns:input message="prijsOrderObj1Request"></b>
                    <soap:body use="encoded" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="urn:tpg_sapxi-wsSAPPocIntf-IwsSAPPoc" />
<b>               </tns:input>
               <tns:output message="prijsOrderObj1Response"></b>
                    <soap:body use="encoded" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="urn:tpg_sapxi-wsSAPPocIntf-IwsSAPPoc" />
               <b></tns:output></b>
          </operation>
     </binding>
     <service name="IwsSAPPocservice">
          <port name="IwsSAPPocPort" binding="tns:IwsSAPPocbinding">
               <soap:address location="http://prid0059.tpgpost.local/SAPPocWebService/SAPPocWebService.exe/soap/IwsSAPPoc" />
          </port>
     </service>
</definitions>

Error while importing WSDL file created in JDeveloper inside BS

Hi All,
I am facing error while importing WSDL of the DBAdapter service created using JDeveloper inside my business service in OSB.
The error in OSB is 'The Resource Mapped Does not exist'

Which version of OSB are you using? You need to upload schema (.xsd) files as well. WSDL has references to that schema(s) but they are not uploaded hence this error. On sbconsole, if you click on a WSDL name to see it, a button comes with name "Edit References". Click that to point to the xsd's you uploaded.
Regards,
Anuj

HTTP error while sending SOAP request using wsdl file

We created SOAP request using the wsdl file ; while sending SOAP request from Altova XMLSpy, we are getting the below error.
HTTP error: could not post file
Can you please explain how to resolve this issue
Regards,
Sanghamitra

there is very little information to help you here.
Can you confirm if this is a SOAP sender scenario or SOAP receiver scenario?
Also do go to thru these links to help you out;
Troubleshooting
Troubleshooting - RFC and SOAP scenarios *** Updated on 20/04/2009 ***
RFC -> SOAP
RFC -> XI -> WebService - A Complete Walkthrough (Part 1)
RFC -> XI -> WebService - A Complete Walkthrough (Part 2)
SOAP <-> XI <-> RFC/BAPI
Walkthrough - SOAP XI RFC/BAPI

Importing WSDL File in Webdynpro abap component

hi experts,
I wanted to use a wsdl in my webdynpro component, ie. in wd java, i can create model and in that i get options to import a wsdl via wsdl file, i have a wsdl file, but how can the same be achived here in wd abap, i could import a functional module, but i dont know how to import wsdl ...
have gone through this url but i could not find the blog.
https://scn.sap.com/thread/502026
Regards
Govardan Raj S

hi Kiran,
The links you have suggested are help full, im completely new to this feild,
here il explain what i did,
i have a wsdl file named as M****_*******_Pzzzz_Baaaaa_Details.wsdl
using se80 i went to my package where my webdyrnpro component is stored.
right click of this pkg, i selected create -> enterprise service /webservice - > proxy object.
here i got a pop with options as 1) consumer Group 2) Exception Classes 3) Service Provider 4) Service Consumer 5) Data Types 6) Data Types Enhancements
i selected service consumer , coz i wanted to consume wsdl.
then on click of continue ,
here i selected Local File radion button.
then browse my wsdl file in my computer, then gave prefix as zbaadtlprxy
and assigned a package and request that im using currently and completed.
now i created a proxy object with name available as
M****_C*********_P*******_Batch_D .
i activated the same.
now after this what is the next step. ?

FB3B2 unable to import WSDL files that contain XSD imports

Much to my dismay, the new WSDL import wizard does not seem
to work on WSDL files that import XSD files. When "Finish" is
pressed, an error dialog states "The WSDL definition could not be
parsed. The wizard cannot complete successfully."
I created a sample WSDL that uses the most basic of XSD
files to demonstrate. Remove the import line from the WSDL and it
will import, with the line it will not.

Hi Jeff,
How are you specifying the WSDL URI?
- If as an absolute path on your machine, make sure there are
no spaces in that path – there is a known issue about path
with spaces and WSDL with imports, and we’re on it. We tried
out your sample WSDL this way and it works.
- If you are specifying it as an HTTP url (accessing it over
the Apache HTTP server, for example), the workaround is a little
more complicated. There are indeed some unresolved issues with the
ActionScript generator. Try putting the wsdl and xsd files inside a
folder in the webroot, and another copy of the xsd in the webroot.
This worked for me - the problem is about locating the imported
document correctly: the introspection correctly uses the sibling
xsd file, while the generator incorrectly looks for that file one
level up. We’ll look into this and fix it.
Please let me know if it starts working or if it still does
not generate the ActionScript client classes. Thank you.
Also, please be aware of another known issue about WSDL with
imports:
http://bugs.adobe.com/jira/browse/FB-7678
(For WSDLs that import other documents, the cached WSDL file should
include the content of the imported documents).
Lacra

Sender SOAP Adaptor - how to use an imported WSDL file

I have to implement an inbound soap interface between my client and its external customer.This interface is in place with the legacy system,which has a webservice that the external customer invokes to send us data.
Now the problem im facing is, the external customer is not willing to change anything on their end (like using our new webservice) except the connection URL,user name and password.(which makes sense too)
I have the WSDL which is currently used imported in XI but has all different namespaces,SOAP address location etc and if I use the messages in the WSDL as it is as my source then its failing in my message mapping.I cannot create the same schema (data type and message type) because the current WSDL root element and some other elements start with a _
Thanks in advance for advices on how to go about it.
Mat

Hi Joseph,
I've had problems importing and using certain WSDL's too, and needed to create my own datatypes and service interfaces to circumvent the problem, using my own namespaces. In order not to have any problems with the namespaces used by the sender, I used the anonymizer bean in the soap adapter module.
I didn't understand what you meant by elements starting with 'a_'. Is the sender using different element names in the WSDL than in the XML sent ? Perhaps you can show us the WSDL and an incoming test message ?
kr,
Peter Glas

Creation of WSDL file & import it in the creation of automated activity

Hi Friends,
I want to create BPM process for automated activity.I have created task for human activity. I have created CAF Application,but I dont know how to ceate/import WSDL file(This WSDL file is used to assign the interface to the automated activity).Can anyone explain about WSDL file creation and it's significance.
(I am following one document 'Creating BPM Process with Human and Automated Activities' from this link ' https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/501bd56f-a5a6-2b10-4fbf-a61a64055fe4')
Regards,
Pranjali

Hi Pranjali,
WSDL is a document written in XML. The document describes a Web service. It specifies the location of the service and the operations (or methods) the service exposes. WSDL types are used to describe the data. XML Schema is used (inline or referenced) for this purpose.
Refer to the below link for more deatils on WSDL:
http://en.wikipedia.org/wiki/Web_Services_Description_Language
Also there are numerous documents avaiable on this topic, just do a google search.
Hope this helps!!
Cheers,
Arafat

Have a requirement to consume a SOAP webservice (wsdl file) using apex

Hi,
I am using Application Express 4.2.2.00.11.
My requirement is to consume a soap web service (wsdl file).
I am pasting the wsdl fille.
<wsdl:message name="FulfillOrderResponseRequestMessage">
<wsdl:part name="payload" element="ffebm:ProcessFulfillmentOrderNotificationEBM"/>
</wsdl:message>
<wsdl:message name="FulfillOrderResponseResponseMessage">
<wsdl:part name="payload" element="ffebm:ProcessFulfillmentOrderNotificationResponseEBM"/>
</wsdl:message>
<wsdl:portType name="FulfillOrderResponse">
<wsdl:operation name="process">
<wsdl:input message="client:FulfillOrderResponseRequestMessage"/>
</wsdl:operation>
</wsdl:portType>
<wsdl:portType name="FulfillOrderResponseCallback">
<wsdl:operation name="processResponse">
<wsdl:input message="client:FulfillOrderResponseResponseMessage"/>
</wsdl:operation>
</wsdl:portType>
<wsdl:binding name="FulfillOrderResponseBinding" type="client:FulfillOrderResponse">
<soap:binding transport="http://schemas.xmlsoap.org/soap/http"/>
<wsp:PolicyReference URI="#wss11_saml_or_username_token_with_message_protection_service_policy" wsdl:required="false"/>
<wsp:PolicyReference URI="#wsaddr_policy" wsdl:required="false"/><wsdl:operation name="process">
and the xml file looks like this
<FulfillOrderResponseRequestMessage>
<part name="payload">
<coreforderrocessFulfillmentOrderNotificationEBM>
<corecom:EBMHeader>
<corecom:EBMID>2d383135353332303931343330383630</corecom:EBMID>
<corecom:EBMName>{_http://xmlns.oracle.com/EnterpriseObjects/Core/EBO/FulfillmentOrder/V1}ProcessFulfillmentOrderNotificationEBM</corecom:EBMName>
<corecom:EBOName>{_http://xmlns.oracle.com/EnterpriseObjects/Core/EBO/FulfillmentOrder/V1}ProcessFulfillmentOrderNotificationEBO</corecom:EBOName>
<corecom:CreationDateTime>2013-12-27T13:29:04.530+05:30</corecom:CreationDateTime>
<corecom:VerbCode>Update</corecom:VerbCode>
<corecom:MessageProcessingInstruction>
<corecom:EnvironmentCode>PRODUCTION</corecom:EnvironmentCode>
</corecom:MessageProcessingInstruction>
<corecomender>
<corecom:ID schemeAgencyID="GPR">EBSVIS</corecom:ID>
<corecomenderMessageID/>
<corecom:CallingServiceName>{_http://xmlns.oracle.com/ApplicationBusinessFlow/OrderToCash/ProcessFulfillmentOrderNotificationEbizToFusionDOOABF/V1}ProcessFulfillmentOrderNotificationEbizToFusionDOOABF</corecom:CallingServiceName>
<corecom:WSAddress>
<ns1:ReplyTo>
<ns1:Address/>
<ns1ortType>ProcessFulfillmentOrderNotificationEbizToFusionDOOABF</ns1ortType>
<ns1erviceName>ProcessFulfillmentOrderNotificationEbizToFusionDOOABF</ns1erviceName>
</ns1:ReplyTo>
<ns1:FaultTo>
<ns1:Address/>
<ns1ortType>ProcessFulfillmentOrderNotificationEbizToFusionDOOABF</ns1ortType>
<ns1erviceName>ProcessFulfillmentOrderNotificationEbizToFusionDOOABF</ns1erviceName>
</ns1:FaultTo>
</corecom:WSAddress>
</corecomender>
<corecom:Target>
<corecom:ID schemeAgencyID="GPR">GPR</corecom:ID>
</corecom:Target>
<corecom:BusinessScope/>
<corecom:EBMTracking>
<corecomequenceNumber>1</corecomequenceNumber>
<corecom:ExecutionUnitName>ProcessFulfillmentOrderNotificationEbizToFusionDOOABF</corecom:ExecutionUnitName>
<corecom:ImplementationCode>BPEL</corecom:ImplementationCode>
<corecom:ActivityDateTime>2013-12-27T13:29:04.531+05:30</corecom:ActivityDateTime>
</corecom:EBMTracking>
<xacml-context:Request/>
</corecom:EBMHeader>
<coreforderataArea>
<corecomrocess operation="ProcessFulfillmentOrderNotification"/>
<coreforderrocessFulfillmentOrderNotification>
<corecom:Identification>
<corecom:BusinessComponentID/>
<corecom:ID schemeID="ORDER_NUMBER" schemeAgencyID="EBSVIS">66498</corecom:ID>
<corecom:ApplicationObjectKey>
<corecom:ID schemeID="HEADER_ID" schemeAgencyID="EBSVIS">228338</corecom:ID>
</corecom:ApplicationObjectKey>
<corecom:AlternateObjectKey>
<corecom:ID schemeAgencyID="GPR">300000030196926</corecom:ID>
</corecom:AlternateObjectKey>
<corecom:AlternateObjectKey>
<corecom:ID schemeID="ExternalInteractionKey">228338</corecom:ID>
</corecom:AlternateObjectKey>
</corecom:Identification>
<coreforder:CurrencyCode listAgencyID="EBSVIS">USD</coreforder:CurrencyCode>
<coreforder:TypeCode listAgencyID="GPR">ORDER</coreforder:TypeCode>
<corecom:BusinessUnitReference>
<corecom:BusinessUnitIdentification>
<corecom:BusinessComponentID/>
<corecom:ApplicationObjectKey>
<corecom:ID schemeID="ORG_ID" schemeAgencyID="EBSVIS">204</corecom:ID>
</corecom:ApplicationObjectKey>
<corecom:AlternateObjectKey>
<corecom:ID schemeAgencyID="GPR">300000028235904</corecom:ID>
</corecom:AlternateObjectKey>
</corecom:BusinessUnitIdentification>
</corecom:BusinessUnitReference>
<coreforder:FulfillmentOrderLine actionCode="UPDATE">
<corecom:Identification>
<corecom:BusinessComponentID/>
<corecom:ID schemeID="LINE_NUMBER" schemeAgencyID="EBSVIS">1</corecom:ID>
<corecom:ApplicationObjectKey>
<corecom:ID schemeID="LINE_ID" schemeAgencyID="EBSVIS">419300</corecom:ID>
</corecom:ApplicationObjectKey>
<corecom:AlternateObjectKey>
<corecom:ID schemeAgencyID="GPR">300000030196928</corecom:ID>
</corecom:AlternateObjectKey>
<corecom:AlternateObjectKey>
<corecom:ID schemeID="ExternalInteractionKey">419300</corecom:ID>
</corecom:AlternateObjectKey>
</corecom:Identification>
<coreforderrderQuantity>2</coreforderrderQuantity>
<coreforder:CurrencyCode listAgencyID="EBSVIS">USD</coreforder:CurrencyCode>
<corecomtatus>
<corecom:Code listAgencyID="GPR">AWAIT_SHIP</corecom:Code>
</corecomtatus>
<corecom:ItemReference>
<corecom:ItemIdentification>
<corecom:BusinessComponentID/>
<corecom:ApplicationObjectKey>
<corecom:ID schemeAgencyID="EBSVIS">225</corecom:ID>
</corecom:ApplicationObjectKey>
</corecom:ItemIdentification>
<corecom:TypeCode listAgencyID="GPR">4</corecom:TypeCode>
</corecom:ItemReference>
<coreforder:FulfillmentOrderSchedule actionCode="UPDATE">
<corecom:Identification>
<corecom:BusinessComponentID/>
<corecom:ApplicationObjectKey>
<corecom:ID schemeID="LINE_ID" schemeAgencyID="EBSVIS">419300</corecom:ID>
</corecom:ApplicationObjectKey>
<corecom:AlternateObjectKey>
<corecom:ID schemeID="FulfillLineId" schemeAgencyID="GPR">300000030196928</corecom:ID>
</corecom:AlternateObjectKey>
<corecom:AlternateObjectKey>
<corecom:ID schemeID="ExternalInteractionKey">419300</corecom:ID>
</corecom:AlternateObjectKey>
</corecom:Identification>
<coreforder:FreightTermCode listAgencyID="EBSVIS">Paid</coreforder:FreightTermCode>
<coreforderrderQuantity>2</coreforderrderQuantity>
<coreforderromisedShipDateTime>2013-12-27T19:30:00.000+00:00</coreforderromisedShipDateTime>
<corefordercheduledShipDateTime>2013-12-27T19:30:00.000+00:00</corefordercheduledShipDateTime>
<corecomtatus>
<corecom:Code listAgencyID="GPR">AWAIT_SHIP</corecom:Code>
</corecomtatus>
<corecom:UnitListPrice>
<corecom:Amount>100</corecom:Amount>
</corecom:UnitListPrice>
<corecom:UnitSalePrice>
<corecom:Amount>100</corecom:Amount>
</corecom:UnitSalePrice>
<corecom:CarrierPartyReference>
<corecomartyIdentification>
<corecom:ApplicationObjectKey>
<corecom:ID schemeAgencyID="EBSVIS"/>
</corecom:ApplicationObjectKey>
</corecomartyIdentification>
</corecom:CarrierPartyReference>
<coreforder:FulfillmentOrderScheduleTax>
<corecom:Tax>
<corecom:Amount>0</corecom:Amount>
</corecom:Tax>
</coreforder:FulfillmentOrderScheduleTax>
<coreforder:FulfillmentOrderItem>
<corecom:ItemReference>
<corecom:ItemIdentification>
<corecom:BusinessComponentID/>
<corecom:ApplicationObjectKey>
<corecom:ID schemeAgencyID="EBSVIS">225</corecom:ID>
</corecom:ApplicationObjectKey>
</corecom:ItemIdentification>
<corecom:TypeCode listAgencyID="GPR">4</corecom:TypeCode>
</corecom:ItemReference>
</coreforder:FulfillmentOrderItem>
</coreforder:FulfillmentOrderSchedule>
</coreforder:FulfillmentOrderLine>
</coreforderrocessFulfillmentOrderNotification>
</coreforderataArea>
</coreforderrocessFulfillmentOrderNotificationEBM>
</part>
</FulfillOrderResponseRequestMessage>
I need to pass few of the above parameters from database using apex.
Any help will be very thankfull.
Please if anything more is required to be provided from my side
Thanks
Nilesh

I nee to pass values to few of the above parameters.
Please inform if anything more is required from my end.

How to get contents of Soap Over JMS web service's wsdl file

Hi,
Is there a way to get the soap over jms webservice's wsdl file in browser? if yes please provide me the details how to get it.
OR how can i get the contensts of WSDL file for soap over jms wsdl file.
thanks in advance.

I have the same question ("Assuming I can generate a wsdl file, can I recreate the SOAP request message from the WSDL file automatically (that matches the original request, which is hand build by me?)")
Have you already found an answer to this?

PI does not combine .wsdl file with .xsd files.

Hi,
I imported .wsdl file with necessary .xsd files in PI system (7.1).
PI does not find fields in .wsdl already necessary .xsd files imported with .wsdl file.
Is there anyone to help me to solve problem with test it in PI system.
I send .wsdl file and necessary .xsd files as attachment his mail address.
Thanks.

Did you try opening the wsdl file in some XML tool...if there is problem in referring the XSD then it will be visible in the tool itself.....even I am working on PI7.1 and some of the WSDLs are referring XSDs...and i had no problem in using them.....dont know what is failing in your case
Do you want me to send .wsdl and .xsd files zipped into your mail box
instead you can post your wsdl file and the corresponding XSD here in SDN....even a dummy structure would do....we are not allowed to do personal email comunication
Regards,
Abhishek.

SOAP Adapterd --importing wsdl file

Similar Messages

Maybe you are looking for