External definition import WSDL complex type problem

Hi,
i have created a webservice using apache axis and created an external definition for the service. You can see the respective WSDL recognized by XI below. The service takes an array of adresses. Unfortunately, when I want to define the message mapping, theres only the array but not the address attributes. What would be a proper definition of the service?
Cheers,
Heiko
===================================================
1. WSDL from external defintion:
<?xml version="1.0" encoding="ISO-8859-1"?>
<wsdl:definitions xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" targetNamespace="http://localhost:8080/axis/services/AdressService">
     <wsdl:types>
          <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://localhost:8080/axis/services/AdressService" targetNamespace="http://localhost:8080/axis/services/AdressService">
               <xsd:import namespace="http://schemas.xmlsoap.org/soap/encoding/" />
               <xsd:complexType xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" name="AddressDto">
                    <xsd:sequence>
                         <xsd:element name="ID" type="xsd:string" nillable="true" />
                         <xsd:element name="name" type="xsd:string" nillable="true" />
                         <xsd:element name="strasse" type="xsd:string" nillable="true" />
                         <xsd:element name="ort" type="xsd:string" nillable="true" />
                    </xsd:sequence>
               </xsd:complexType>
               <xsd:complexType xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" name="ArrayOfAddressDto">
                    <xsd:complexContent>
                         <xsd:restriction base="soapenc:Array">
                              <xsd:attribute ref="soapenc:arrayType" wsdl:arrayType="impl:AddressDto[]" />
                         </xsd:restriction>
                    </xsd:complexContent>
               </xsd:complexType>
          </xsd:schema>
     </wsdl:types>
     <wsdl:message name="writeAddressDataResponse" />
     <wsdl:message name="writeAddressDataRequest">
          <wsdl:part xmlns:generateduniqueprefix3="http://localhost:8080/axis/services/AdressService" name="addresses" type="generateduniqueprefix3:ArrayOfAddressDto" />
     </wsdl:message>
</wsdl:definitions>
2. XSD extracted from WSDL:
<?xml version="1.0" encoding="UTF-8"?>
<xsd:schema targetNamespace="http://localhost:8080/axis/services/AdressService" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://localhost:8080/axis/services/AdressService">
  <xsd:import namespace="http://schemas.xmlsoap.org/soap/encoding/" />
  <xsd:element name="addresses" type="ArrayOfAddressDto" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" />
  <xsd:complexType name="ArrayOfAddressDto" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/">
    <xsd:complexContent>
      <xsd:restriction base="soapenc:Array">
        <xsd:attribute ref="soapenc:arrayType" wsdl:arrayType="impl:AddressDto[]" xmlns:xsd="http://www.w3.org/2001/XMLSchema" />
      </xsd:restriction>
    </xsd:complexContent>
  </xsd:complexType>
</xsd:schema>
??? Where are the atributes of the address here ???

Hi Heiko,
XI does not support the use of soapenc:array. Please refer to http://www.ws-i.org/Profiles/BasicProfile-1.0-2004-04-16.html#refinement16556272 regarding the use of this construct.
Greetings Stephan

Similar Messages

  • Error while Creating External definition with WSDL file

    Hi ALL,
    I need to create a External defination with a WSDL file in PI 7.1.so i selected the Option WSDL & From all available message defination while creating External defination  & imported the WSDL file.
    I am getting an error
    javax.ejb.EJBException: nested exception is: java.lang.RuntimeException: java.lang.NoSuchMethodError: com.sap.aii.utilxi.wsdl.api.WsdlHandler.parseWsdlWithOrderRearrange(Lcom/sap/aii/utilxi/xml/xdom/XElement;Z)Lcom/sap/aii/utilxi/wsdl/api/Wsdl; java.lang.RuntimeException: java.lang.NoSuchMethodError:
    Note : i checked the WSDl file in altova its no error's ,i know there is no problem with the WSDL file ,i tried importing the same in other XI 3.0 system it has no problem.
    help me in solving this ..
    Regards
    Shakeif

    Hi Tony,
    Somehow I solved this issue. I dont remember what exactly I did, as it was sometime back in December. I think I used the Wizard initially to do the configurations in Solution Manager and again i tried to do the same manually as the earlier one threw some errors.
    It seems the wizard proceeded half-way through and hence the entry was made in the database already and hence that error.
    Anyways thank you for replying me.
    best regds,
    Alagammai.

  • External definitions import into Message mapping

    Hi,
    I have a DTD message in external definitions to be imported into the message mapping. But I am not able to choose the object in the mapping editor. It does not allow even if the message is a valid WSDL. The only time it allows to import into the message editor is when its an XSD.I am not sure why the external definitions in DTD or WSDL formats are not able to be imported or am I missing something??
    -Ken

    Hi,
      A conversion of the downloaded cXML DTD into XSD by using XMLSPY yields 3 XSD files. Using the initial XSD(which has the major fields) yields the same error(i.e cannot create messages or valid WSDL) in external definitions.
    I also tried using one of the standard xml's from the cXML site and the funny part was XMLSPY validated them without errors and while importing them directly into the mapping editor, XI throws an error "XML NOT WELL FORMED". Its so weird.
      Also is there a possibility to write a script to manipulate the payload message after passing through the adapters? For eg : Creating a script which will delete a valid tag in payload before it reaches the 3rd party. ...By adding the DOCTYPE in the prolog, the message would look like this :
    "<?xml...utf-8>
    <!DOCTYPE......'Cxml.org'>
    <?xml.....utf-8>
    <start tag></start tag>”
    Therefore some kind of a script that would remove the second <?xml tag on line 3>..
    This is just a round about thinking…
    Any ideas..

  • 2 level schema import: cvc-complex-type.2.4.a: Invalid content was found...

    HI
    I'm writing an application that gathers xml documents into batches, sends these batches to translation, receives them from translation and unpacks them.
    My documents are ads. I have a schema (x1.xsd) describing them. This schema imports another schema (x2.xsd). None of these are controlled by me (I need a very good reason to change them).
    I have created a new schema (x.xsd) for my batches. This schma imports the ad schema (x1.xsd).
    When I validate an example ad (x1.xml) using the ad schema (x1.xsd), validation is OK. This is the same for XML Spy, oracle.xml.schemavalidator.XSDValidator and org.dom4j.io.SAXReader
    When I validate an example batch (x.xml) with the same ad data in the batch,
    XML Spy says: Unexpected element 'AD' in element 'ADS'. Expected: AD
    oracle.xml.schemavalidator.XSDValidator says: XML-24521: (Error) Element not completed: 'ADS'org.dom4j.io.SAXReader says: cvc-complex-type.2.4.a: Invalid content was found starting with element 'AD'. One of '{"x/translation":AD}' is expected.
    By changing my batch xml by removing xmlns="x/ad" from the AD tag and prefix all "x/ad"-owned tags with ad:, I can make all validators validate.
    But I don't see the reason for this, and thus have some problems telling the supplier that we need to change the schema and xml...
    Notice that I do not have the corresponding problem in the x1.xsd / x2.xsd relationship !!??
    Any suggestions will be appreciated.
    /Jornsen
    I enclose a copy of the files mentioned above:
    x.xml:
    <TRANSLATION_BATCH batchId="8" xmlns="x/translation" xmlns:ad="x/ad" xmlns:gp="x/groups"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:tl="x/translation" xsi:schemaLocation="x/translation
    C:\tmp\t.xsd">
      <LANGUAGES anattr="monoLanguageXmlAd">
        <LANG LangId="3"/>
        <LANG LangId="4"/>
      </LANGUAGES>
      <ADS>
        <AD adattr="hest" xmlns="x/ad" xmlns:gp="x/groups" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
          <LANGLIST>
            <LANG LangId="17"/>
          </LANGLIST>
          <ITEMLIST>
            <ITEM xmlns="x/groups" anattr="hund">
              <ITEM_INFO name="hest"/>
            </ITEM>
          </ITEMLIST>
        </AD>
      </ADS>
    </TRANSLATION_BATCH>x1.xml:
    <AD adattr="hest" xmlns="x/ad" xmlns:gp="x/groups" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:schemaLocation="x/ad C:\tmp\t1.xsd">
      <LANGLIST>
        <LANG LangId="17"/>
      </LANGLIST>
      <ITEMLIST>
        <ITEM xmlns="x/groups" anattr="hund">
          <ITEM_INFO name="hest"/>
        </ITEM>
      </ITEMLIST>
    </AD>x.xsd:
    <xs:schema targetNamespace="x/translation" attributeFormDefault="unqualified" elementFormDefault="qualified"
    xmlns="x/translation" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:tl="x/translation" xmlns:ad="x/ad">
      <xs:import namespace="x/ad" schemaLocation="t1.xsd"/>
      <xs:element name="TRANSLATION_BATCH">
        <xs:complexType>
          <xs:sequence>
            <xs:element name="LANGUAGES">
              <xs:complexType>
                <xs:sequence>
                  <xs:element name="LANG" maxOccurs="unbounded">
                    <xs:complexType>
                      <xs:attribute name="LangId" type="xs:string" use="required"/>
                    </xs:complexType>
                  </xs:element>
                </xs:sequence>
                <xs:attribute name="anattr" type="xs:string"/>
              </xs:complexType>
            </xs:element>
            <xs:element name="ADS">
              <xs:complexType>
                <xs:sequence>
                  <xs:element name="AD" type="ad:ADType"/>
                </xs:sequence>
              </xs:complexType>
            </xs:element>
          </xs:sequence>
          <xs:attribute name="batchId" type="xs:string" use="required"/>
        </xs:complexType>
      </xs:element>
    </xs:schema>x1.xsd:
    <xs:schema targetNamespace="x/ad" attributeFormDefault="unqualified" elementFormDefault="qualified" xmlns="x/ad"
    xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:ad="x/ad" xmlns:gp="x/groups">
      <xs:import namespace="x/groups" schemaLocation="t2.xsd"/>
      <xs:element name="AD" type="ad:ADType">
      </xs:element>
      <xs:complexType name="ADType">
        <xs:sequence>
          <xs:element name="LANGLIST" type="ad:LANGLISTType">
          </xs:element>
          <xs:element name="ITEMLIST" type="gp:ITEMLISTType">
          </xs:element>
        </xs:sequence>
        <xs:attribute name="adattr" type="xs:string" use="optional"/>
      </xs:complexType>
      <xs:complexType name="LANGType">
        <xs:attribute name="LangId" type="xs:int" use="required"/>
      </xs:complexType>
      <xs:complexType name="LANGLISTType">
        <xs:sequence>
          <xs:element name="LANG" type="ad:LANGType" maxOccurs="unbounded"/>
        </xs:sequence>
      </xs:complexType>
    </xs:schema>x2.xsd:
    <xs:schema xmlns="x/groups" xmlns:xs="http://www.w3.org/2001/XMLSchema" targetNamespace="x/groups"
    elementFormDefault="qualified" attributeFormDefault="unqualified">
      <xs:complexType name="ITEMLISTType">
        <xs:sequence>
          <xs:element name="ITEM" minOccurs="0" maxOccurs="unbounded">
            <xs:complexType>
              <xs:sequence>
                <xs:element name="ITEM_INFO" maxOccurs="unbounded">
                  <xs:complexType>
                    <xs:attribute name="name" type="xs:string" use="required"/>
                  </xs:complexType>
                </xs:element>
              </xs:sequence>
              <xs:attribute name="anattr" type="xs:string"/>
            </xs:complexType>
          </xs:element>
        </xs:sequence>
      </xs:complexType>
    </xs:schema>Message was edited by:
    Jornsen - formatting
    Message was edited by:
    Jornsen

    Hi Linyin,
    Please refer to: http://middlewaremagic.com/weblogic/?p=2034
    The Problem is missing element <web-resource-name> in your "web.xml" file..... which must be a Unique name of your Resource set which u want to make secure.....
    <security-constraint>
    <web-resource-collection>
    *<web-resource-name>MySecureResources</web-resource-name>*
    <description>Some Description</description>
    <url-pattern>/*</url-pattern>
    <http-method>GET</http-method>
    <http-method>POST</http-method>
    </web-resource-collection>
    <auth-constraint>
    <role-name>admin</role-name>
    </auth-constraint>
    </security-constraint>
    <login-config>
    <auth-method>BASIC</auth-method>
    </login-config>
    <security-role>
    <role-name>admin</role-name>
    </security-role>
    Thanks
    Jay SenSharma
    http://middlewaremagic.com/weblogic   (Middleware Magic Is Here)

  • External Definition (wsdl) with abstract xsd element

    Hello All,
    we are trying to call a webservice, here is the wsdl:
    https://www.1link.com/fr/demo-sn/site/gaiwebservice.asmx?WSDL
    the problem is that the GAIJobLine element is defined as abstract:
    <s:complexType name="GAIJobLine" abstract="true">
    and there several elements which are extending GAIJobLine, for example:
    <s:complexType name="GAITyreLine">
                        <s:complexContent mixed="false">
                             <s:extension base="tns:GAIJobLine">
    So in our mapping we need to map to those element which are extending base element and not to the abstract one, but Graphical mapping displays only GAIJobLIne base element.
    Does anybody know how we can map to extended elements without mannually changing wsdl?
    Best Regards,
    Artsiom Anichenka

    thanks for your reply!
    the extended elements are seen when I open wsdl in XMLSpy.
    they are also visible in external definition object, but the main problem is that in the mapping only the base lement is displayed and there is no possobility to choose the extension.
    Maybe this kind os XSDs (with abstract base types and extended elements) are just not supported by PI711?

  • Possible? Using External Definitions for data type/message type definitions

    Hi all,
    i want to use external definitons in my own data type definitions. Is that possible? And if yes, how?
    I imported many definitions via a mass import. Now I also want to use these definitions for further interfaces (than the imported ones). The most convenient would be of course to just use them as a custom created type. Can I somehow "convert" an external definition to a data type/message type?
    KR
    Felix

    Hello Felix,
          The External defination which you has been imported that cant use in DT and MT but yeah you can use this in Service interface.
    you cant modify that External defination if you want to do that then 1st of all modify it and then reimport it as an another external defination.
    and creating service interface with this ED you can use it in your message mapping .
    i hope this will help to you to clear your doubt.
    Monica

  • How to see structure under schema when Create External Definition

    Hi ...we have scenario like RFC<>XI<>SOAP
    The request payload(SOAPIN) for SOAP is:
    <?xml version="1.0" encoding="utf-8"?>
    <soap:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
      <soap:Body>
        <AddressValidator xmlns="http://tempuri.org/geostan3/AddressValidator">
          <LicenseFile>string</LicenseFile>
           <Z9Path>string</Z9Path>
          <House>string</House>
          <Street>string</Street>
            </soap:Body>
    </soap:Envelope>
    and we are expecting response message from SOAP:
    diffgr:diffgram xmlns:msdata="urn:schemas-microsoft-com:xml-msdata" xmlns:diffgr="urn:schemas-microsoft-com:xml-diffgram-v1">
    - <AddressCheck xmlns="">
    - <Address diffgr:id="Address1" msdata:rowOrder="0" diffgr:hasChanges="inserted">
      <Addline1>220 W MAIN ST</Addline1>
      <Addline2 />
      <URB />
      <Lastline>LOUISVILLE, KY 40202-1395</Lastline>
      <Location>-85754010, 38256144</Location>
      <OutBlock>211110049001067</OutBlock>
      <OutCBSA>31140</OutCBSA>
      <MatchCode>SE0</MatchCode>
      <LocationCode>AS0</LocationCode>
      <DPVConfirm />
      <FootNote1 />
      <FootNote2 />
      <FootNote3 />
      <Msg>OK</Msg>
      </Address>
      </AddressCheck>
    so when we created external definition  using  wsdl file into XI, it showing only schema as SOAPOUT  (I couldn't see those fields in XI/under schema).
    <?xml version="1.0" encoding="utf-8"?>
    <soap:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
      <soap:Body>
        <AddressValidatorResponse xmlns="http://tempuri.org/geostan3/AddressValidator">
          <AddressValidatorResult>
            <xsd:schema>schema</xsd:schema>xml</AddressValidatorResult>
        </AddressValidatorResponse>
      </soap:Body>
    </soap:Envelope>
    SXMB_MONI showing(Response):
    <?xml version="1.0" encoding="UTF-8" ?>
    - <ns0:AddressValidatorResponse xmlns:ns0="http://tempuri.org/geostan3/AddressValidator">
    - <ns0:AddressValidatorResult>
      <ns1:schema xmlns:ns1="http://www.w3.org/2001/XMLSchema" />
      </ns0:AddressValidatorResult>
      </ns0:AddressValidatorResponse>
    So my question is how do I map response fields to RFC response? Auctully this schema is like table structure which is having all response fields.
    I could see all response structure with data in sxmb_moni-->Response Msg ID > inbound message>payloads(main document). Is there any way to send this response to RFC ?
    or can you suggest me any other way to send this response to RFC.
    Thanks,
    Edited by: PILearn on Jun 2, 2008 10:21 PM

    Here you go..
    <?xml version="1.0" encoding="utf-8"?>
    <wsdl:definitions xmlns:http="http://schemas.xmlsoap.org/wsdl/http/" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:s="http://www.w3.org/2001/XMLSchema" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:tns="http://tempuri.org/geostan3/AddressValidator" xmlns:tm="http://microsoft.com/wsdl/mime/textMatching/" xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/" targetNamespace="http://tempuri.org/geostan3/AddressValidator" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/">
      <wsdl:types>
        <s:schema elementFormDefault="qualified" targetNamespace="http://tempuri.org/geostan3/AddressValidator">
          <s:import namespace="http://www.w3.org/2001/XMLSchema" />
          <s:element name="AddressValidator">
            <s:complexType>
              <s:sequence>
                <s:element minOccurs="0" maxOccurs="1" name="LicenseFile" type="s:string" />
                <s:element minOccurs="0" maxOccurs="1" name="LicensePassword" type="s:string" />
                <s:element minOccurs="0" maxOccurs="1" name="SearchPath" type="s:string" />
                <s:element minOccurs="0" maxOccurs="1" name="Z9Path" type="s:string" />
                <s:element minOccurs="0" maxOccurs="1" name="House" type="s:string" />
                <s:element minOccurs="0" maxOccurs="1" name="Street" type="s:string" />
                <s:element minOccurs="0" maxOccurs="1" name="AddLine2" type="s:string" />
                <s:element minOccurs="0" maxOccurs="1" name="AddLastLine" type="s:string" />
                <s:element minOccurs="0" maxOccurs="1" name="URB" type="s:string" />
                <s:element minOccurs="0" maxOccurs="1" name="Matchmode" type="s:string" />
                <s:element minOccurs="0" maxOccurs="1" name="Datum" type="s:string" />
              </s:sequence>
            </s:complexType>
          </s:element>
          <s:element name="AddressValidatorResponse">
            <s:complexType>
              <s:sequence>
                <s:element minOccurs="0" maxOccurs="1" name="AddressValidatorResult">
                  <s:complexType>
                    <s:sequence>
                      <s:element ref="s:schema" />
                      <s:any />
                    </s:sequence>
                  </s:complexType>
                </s:element>
              </s:sequence>
            </s:complexType>
          </s:element>
          <s:element name="DataSet" nillable="true">
            <s:complexType>
              <s:sequence>
                <s:element ref="s:schema" />
                <s:any />
              </s:sequence>
            </s:complexType>
          </s:element>
        </s:schema>
      </wsdl:types>
      <wsdl:message name="AddressValidatorSoapIn">
        <wsdl:part name="parameters" element="tns:AddressValidator" />
      </wsdl:message>
      <wsdl:message name="AddressValidatorSoapOut">
        <wsdl:part name="parameters" element="tns:AddressValidatorResponse" />
      </wsdl:message>
      <wsdl:message name="AddressValidatorHttpGetIn">
        <wsdl:part name="LicenseFile" type="s:string" />
        <wsdl:part name="LicensePassword" type="s:string" />
        <wsdl:part name="SearchPath" type="s:string" />
        <wsdl:part name="Z9Path" type="s:string" />
        <wsdl:part name="House" type="s:string" />
        <wsdl:part name="Street" type="s:string" />
        <wsdl:part name="AddLine2" type="s:string" />
        <wsdl:part name="AddLastLine" type="s:string" />
        <wsdl:part name="URB" type="s:string" />
        <wsdl:part name="Matchmode" type="s:string" />
        <wsdl:part name="Datum" type="s:string" />
      </wsdl:message>
      <wsdl:message name="AddressValidatorHttpGetOut">
        <wsdl:part name="Body" element="tns:DataSet" />
      </wsdl:message>
      <wsdl:message name="AddressValidatorHttpPostIn">
        <wsdl:part name="LicenseFile" type="s:string" />
        <wsdl:part name="LicensePassword" type="s:string" />
        <wsdl:part name="SearchPath" type="s:string" />
        <wsdl:part name="Z9Path" type="s:string" />
        <wsdl:part name="House" type="s:string" />
        <wsdl:part name="Street" type="s:string" />
        <wsdl:part name="AddLine2" type="s:string" />
        <wsdl:part name="AddLastLine" type="s:string" />
        <wsdl:part name="URB" type="s:string" />
        <wsdl:part name="Matchmode" type="s:string" />
        <wsdl:part name="Datum" type="s:string" />
      </wsdl:message>
      <wsdl:message name="AddressValidatorHttpPostOut">
        <wsdl:part name="Body" element="tns:DataSet" />
      </wsdl:message>
      <wsdl:portType name="AddressCheckSoap">
        <wsdl:operation name="AddressValidator">
          <wsdl:input message="tns:AddressValidatorSoapIn" />
          <wsdl:output message="tns:AddressValidatorSoapOut" />
        </wsdl:operation>
      </wsdl:portType>
      <wsdl:portType name="AddressCheckHttpGet">
        <wsdl:operation name="AddressValidator">
          <wsdl:input message="tns:AddressValidatorHttpGetIn" />
          <wsdl:output message="tns:AddressValidatorHttpGetOut" />
        </wsdl:operation>
      </wsdl:portType>
      <wsdl:portType name="AddressCheckHttpPost">
        <wsdl:operation name="AddressValidator">
          <wsdl:input message="tns:AddressValidatorHttpPostIn" />
          <wsdl:output message="tns:AddressValidatorHttpPostOut" />
        </wsdl:operation>
      </wsdl:portType>
      <wsdl:binding name="AddressCheckSoap" type="tns:AddressCheckSoap">
        <soap:binding transport="http://schemas.xmlsoap.org/soap/http" style="document" />
        <wsdl:operation name="AddressValidator">
          <soap:operation soapAction="http://tempuri.org/geostan3/AddressValidator/AddressValidator" style="document" />
          <wsdl:input>
            <soap:body use="literal" />
          </wsdl:input>
          <wsdl:output>
            <soap:body use="literal" />
          </wsdl:output>
        </wsdl:operation>
      </wsdl:binding>
      <wsdl:binding name="AddressCheckHttpGet" type="tns:AddressCheckHttpGet">
        <http:binding verb="GET" />
        <wsdl:operation name="AddressValidator">
          <http:operation location="/AddressValidator" />
          <wsdl:input>
            <http:urlEncoded />
          </wsdl:input>
          <wsdl:output>
            <mime:mimeXml part="Body" />
          </wsdl:output>
        </wsdl:operation>
      </wsdl:binding>
      <wsdl:binding name="AddressCheckHttpPost" type="tns:AddressCheckHttpPost">
        <http:binding verb="POST" />
        <wsdl:operation name="AddressValidator">
          <http:operation location="/AddressValidator" />
          <wsdl:input>
            <mime:content type="application/x-www-form-urlencoded" />
          </wsdl:input>
          <wsdl:output>
            <mime:mimeXml part="Body" />
          </wsdl:output>
        </wsdl:operation>
      </wsdl:binding>
      <wsdl:service name="AddressCheck">
        <wsdl:port name="AddressCheckSoap" binding="tns:AddressCheckSoap">
          <soap:address location="http://sap-ccs-geo02/geostan3/AddressValidator.asmx" />
        </wsdl:port>
        <wsdl:port name="AddressCheckHttpGet" binding="tns:AddressCheckHttpGet">
          <http:address location="http://sap-ccs-geo02/geostan3/AddressValidator.asmx" />
        </wsdl:port>
        <wsdl:port name="AddressCheckHttpPost" binding="tns:AddressCheckHttpPost">
          <http:address location="http://sap-ccs-geo02/geostan3/AddressValidator.asmx" />
        </wsdl:port>
      </wsdl:service>
    </wsdl:definitions>

  • Formatting CF data for a web service complex type

    I am trying to call a web service with the following definition in the WSDL
    <s:element name="CreateDataList">
         <s:complexType>
              <s:sequence>
                   <s:element minOccurs="0" maxOccurs="1" name="client_app_id" type="s:string"/>
                   <s:element minOccurs="0" maxOccurs="1" name="client_app_pwd" type="s:string"/>
                   <s:element minOccurs="1" maxOccurs="1" name="data_template_id" type="s:int"/>
                   <s:element minOccurs="1" maxOccurs="1" name="calculate_persistent_values" type="s:int"/>
                   <s:element minOccurs="0" maxOccurs="1" name="data" type="tns:ArrayOfArrayOfName_value"/>
              </s:sequence>
         </s:complexType>
    </s:element>
    <s:complexType name="ArrayOfArrayOfName_value">
         <s:sequence>
              <s:element minOccurs="0" maxOccurs="unbounded" name="record" type="tns:ArrayOfName_value"/>
         </s:sequence>
    </s:complexType>
    <s:complexType name="ArrayOfName_value">
         <s:sequence>
              <s:element minOccurs="0" maxOccurs="unbounded" name="variable" type="tns:name_value"/>
         </s:sequence>
    </s:complexType>
    <s:complexType name="name_value">
         <s:sequence>
              <s:element minOccurs="0" maxOccurs="1" name="name" type="s:string"/>
              <s:element minOccurs="0" maxOccurs="1" name="value" type="s:string"/>
         </s:sequence>
    </s:complexType>
    I am trying to format the ArrayOfArrayOfName_value data and getting an "argument type mismatch" error. The sample PHP code for the data looks like this:
    $data = array(0 => array(
        array('name' => 'FIRST_NAME', 'value' => 'First'),
        array('name' => 'LAST_NAME', 'value' => 'Last'),
        array('name' => 'ADDRESS', 'value' => 'Address'),
        array('name' => 'CITY', 'value' => 'City'),
        array('name' => 'STATE', 'value' => 'State'),
        array('name' => 'ZIP', 'value' => '55555')
    1 => array(
        array('name' => 'FIRST_NAME', 'value' => 'First'),
        array('name' => 'LAST_NAME', 'value' => 'Last'),
        array('name' => 'ADDRESS', 'value' => 'Address'),
        array('name' => 'CITY', 'value' => 'City'),
        array('name' => 'STATE', 'value' => 'State'),
        array('name' => 'ZIP', 'value' => '55555')
    My CF code looks like this:
    <cfset data = ArrayNew(1) />
    <cfset data[1] = ArrayNew(1) />
    <cfset data[1][1] = StructNew() />
    <cfset data[1][1]["name"] = "NAME" />
    <cfset data[1][1]["value"] = "JOhn Doe" />
    <cfset data[1][2] = StructNew() />
    <cfset data[1][2]["name"] = "ADDRESS1" />
    <cfset data[1][2]["value"] = "123 Test St" />
    <cfset data[1][3] = StructNew() />
    <cfset data[1][3]["name"] = "ADDRESS2" />
    <cfset data[1][3]["value"] = "" />
    <cfset data[1][4] = StructNew() />
    <cfset data[1][4]["name"] = "CITY" />
    <cfset data[1][4]["value"] = "Austin" />
    <cfset data[1][5] = StructNew() />
    <cfset data[1][5]["name"] = "STATE" />
    <cfset data[1][5]["value"] = "TX" />
    <cfset data[1][6] = StructNew() />
    <cfset data[1][6]["name"] = "ZIP" />
    <cfset data[1][6]["value"] = "78704" />
    <cfset data[2] = ArrayNew(1) />
    <cfset data[2][1] = StructNew() />
    <cfset data[2][1]["name"] = "NAME" />
    <cfset data[2][1]["value"] = "Jane Doe" />
    <cfset data[2][2] = StructNew() />
    <cfset data[2][2]["name"] = "ADDRESS1" />
    <cfset data[2][2]["value"] = "987 Test St" />
    <cfset data[2][3] = StructNew() />
    <cfset data[2][3]["name"] = "ADDRESS2" />
    <cfset data[2][3]["value"] = "" />
    <cfset data[2][4] = StructNew() />
    <cfset data[2][4]["name"] = "CITY" />
    <cfset data[2][4]["value"] = "Austin" />
    <cfset data[2][5] = StructNew() />
    <cfset data[2][5]["name"] = "STATE" />
    <cfset data[2][5]["value"] = "TX" />
    <cfset data[2][6] = StructNew() />
    <cfset data[2][6]["name"] = "ZIP" />
    <cfset data[2][6]["value"] = "78704" />
    Any suggestions for where I am going wrong would be greatly appreciated.

    If anyone is interested here is the correct CF format for this WSDL complex type definition
    <cfset data = StructNew() />
    <cfset data["record"] = ArrayNew(1) />
    <cfset data["record"][1] = StructNew() />
    <cfset data["record"][1]["variable"] = ArrayNew(1) />
    <cfset data["record"][1]["variable"][1] = StructNew() />
    <cfset data["record"][1]["variable"][1]["name"] = "NAME" />
    <cfset data["record"][1]["variable"][1]["value"] = "John Doe" />
    <cfset data["record"][1]["variable"][2] = StructNew() />
    <cfset data["record"][1]["variable"][2]["name"] = "ADDRESS1" />
    <cfset data["record"][1]["variable"][2]["value"] = "123 Test St" />
    <cfset data["record"][1]["variable"][3] = StructNew() />
    <cfset data["record"][1]["variable"][3]["name"] = "ADDRESS2" />
    <cfset data["record"][1]["variable"][3]["value"] = "" />
    <cfset data["record"][1]["variable"][4] = StructNew() />
    <cfset data["record"][1]["variable"][4]["name"] = "CITY" />
    <cfset data["record"][1]["variable"][4]["value"] = "Austin" />
    <cfset data["record"][1]["variable"][5] = StructNew() />
    <cfset data["record"][1]["variable"][5]["name"] = "STATE" />
    <cfset data["record"][1]["variable"][5]["value"] = "TX" />
    <cfset data["record"][1]["variable"][6] = StructNew() />
    <cfset data["record"][1]["variable"][6]["name"] = "ZIP" />
    <cfset data["record"][1]["variable"][6]["value"] = "78704" />
    <cfset data["record"][2] = StructNew() />
    <cfset data["record"][2]["variable"] = ArrayNew(1) />
    <cfset data["record"][2]["variable"][1] = StructNew() />
    <cfset data["record"][2]["variable"][1]["name"] = "NAME" />
    <cfset data["record"][2]["variable"][1]["value"] = "Jane Doe" />
    <cfset data["record"][2]["variable"][2] = StructNew() />
    <cfset data["record"][2]["variable"][2]["name"] = "ADDRESS1" />
    <cfset data["record"][2]["variable"][2]["value"] = "987 Test St" />
    <cfset data["record"][2]["variable"][3] = StructNew() />
    <cfset data["record"][2]["variable"][3]["name"] = "ADDRESS2" />
    <cfset data["record"][2]["variable"][3]["value"] = "" />
    <cfset data["record"][2]["variable"][4] = StructNew() />
    <cfset data["record"][2]["variable"][4]["name"] = "CITY" />
    <cfset data["record"][2]["variable"][4]["value"] = "Austin" />
    <cfset data["record"][2]["variable"][5] = StructNew() />
    <cfset data["record"][2]["variable"][5]["name"] = "STATE" />
    <cfset data["record"][2]["variable"][5]["value"] = "TX" />
    <cfset data["record"][2]["variable"][6] = StructNew() />
    <cfset data["record"][2]["variable"][6]["name"] = "ZIP" />
    <cfset data["record"][2]["variable"][6]["value"] = "78704" />

  • 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.

  • Importing WSDL into External Definitions

    Hi,
    I got WSDLs from WAS WS Navigator, I have imported the WSDL from <b>porttypes</b> folder but I don't see any messages in the messages tab of External Definitions.
    See below my WSDL
    <?xml version="1.0" encoding="utf-8"?>
    <!--            Generated by WSDLDefinitionsParser    --><wsdl:definitions xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:ns0="urn:xEM_MeasurementImportVi" targetNamespace="urn:xEM_MeasurementImportWsd/xEM_MeasurementImportVi/document" xmlns:tns="urn:xEM_MeasurementImportWsd/xEM_MeasurementImportVi/document">
      <wsdl:types>
        <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" targetNamespace="urn:java/lang" xmlns:tns="urn:java/lang" elementFormDefault="qualified">
          <xs:complexType name="ArrayOfint">
            <xs:sequence>
              <xs:element maxOccurs="unbounded" minOccurs="0" name="int" type="xs:int" nillable="true"/>
            </xs:sequence>
          </xs:complexType>
          <xs:complexType name="ArrayOfString">
            <xs:sequence>
              <xs:element maxOccurs="unbounded" minOccurs="0" name="String" type="xs:string" nillable="true"/>
            </xs:sequence>
          </xs:complexType>
        </xs:schema>
        <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" targetNamespace="urn:com.technidata.em.imp.consumption" xmlns:tns="urn:com.technidata.em.imp.consumption" elementFormDefault="qualified">
          <xs:complexType name="ReturnCode">
            <xs:sequence>
              <xs:element name="code" type="xs:int"/>
              <xs:element name="description" type="xs:string" nillable="true" minOccurs="0"/>
            </xs:sequence>
          </xs:complexType>
          <xs:complexType name="ArrayOfReturnCode">
            <xs:sequence>
              <xs:element maxOccurs="unbounded" minOccurs="0" name="ReturnCode" type="tns:ReturnCode" nillable="true"/>
            </xs:sequence>
          </xs:complexType>
        </xs:schema>
        <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" targetNamespace="urn:com.technidata.em" xmlns:tns="urn:com.technidata.em" elementFormDefault="qualified">
          <xs:complexType name="Measurement">
            <xs:sequence>
              <xs:element name="pSystemId" type="xs:string" nillable="true" minOccurs="0"/>
              <xs:element name="pSystemTagId" type="xs:string" nillable="true" minOccurs="0"/>
              <xs:element name="pDate" type="xs:dateTime" nillable="true" minOccurs="0"/>
              <xs:element name="pValue" type="xs:double"/>
              <xs:element name="pUnit" type="xs:string" nillable="true" minOccurs="0"/>
              <xs:element name="pDescription" type="xs:string" nillable="true" minOccurs="0"/>
            </xs:sequence>
          </xs:complexType>
          <xs:complexType name="ArrayOfMeasurement">
            <xs:sequence>
              <xs:element maxOccurs="unbounded" minOccurs="0" name="Measurement" type="tns:Measurement" nillable="true"/>
            </xs:sequence>
          </xs:complexType>
        </xs:schema>
        <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" targetNamespace="urn:xEM_MeasurementImportVi" xmlns:tns="urn:xEM_MeasurementImportVi" elementFormDefault="qualified" xmlns:s1="urn:java/lang" xmlns:s2="urn:com.technidata.em.imp.consumption" xmlns:s0="urn:com.technidata.em">
          <xs:import namespace="urn:java/lang"/>
          <xs:import namespace="urn:com.technidata.em.imp.consumption"/>
          <xs:import namespace="urn:com.technidata.em"/>
          <xs:element name="checkConnection">
            <xs:complexType>
              <xs:sequence/>
            </xs:complexType>
          </xs:element>
          <xs:element name="checkConnectionResponse">
            <xs:complexType>
              <xs:sequence>
                <xs:element name="Response" type="xs:string" nillable="true"/>
              </xs:sequence>
            </xs:complexType>
          </xs:element>
          <xs:element name="doMeasurementImport">
            <xs:complexType>
              <xs:sequence>
                <xs:element name="pSystemId" type="xs:string" nillable="true"/>
                <xs:element name="pSystemTagId" type="xs:string" nillable="true"/>
                <xs:element name="pDate" type="xs:dateTime" nillable="true"/>
                <xs:element name="pValue" type="xs:double"/>
                <xs:element name="pUnit" type="xs:string" nillable="true"/>
                <xs:element name="pDescription" type="xs:string" nillable="true"/>
              </xs:sequence>
            </xs:complexType>
          </xs:element>
          <xs:element name="doMeasurementImportResponse">
            <xs:complexType>
              <xs:sequence>
                <xs:element name="Response" type="xs:int"/>
              </xs:sequence>
            </xs:complexType>
          </xs:element>
          <xs:element name="doMeasurementsImport">
            <xs:complexType>
              <xs:sequence>
                <xs:element name="pMeasurements" type="s0:ArrayOfMeasurement" nillable="true"/>
              </xs:sequence>
            </xs:complexType>
          </xs:element>
          <xs:element name="doMeasurementsImportResponse">
            <xs:complexType>
              <xs:sequence>
                <xs:element name="Response" type="s1:ArrayOfint" nillable="true"/>
              </xs:sequence>
            </xs:complexType>
          </xs:element>
          <xs:element name="getErrorCodes">
            <xs:complexType>
              <xs:sequence/>
            </xs:complexType>
          </xs:element>
          <xs:element name="getErrorCodesResponse">
            <xs:complexType>
              <xs:sequence>
                <xs:element name="Response" type="s2:ArrayOfReturnCode" nillable="true"/>
              </xs:sequence>
            </xs:complexType>
          </xs:element>
          <xs:element name="getSupportedUnits">
            <xs:complexType>
              <xs:sequence/>
            </xs:complexType>
          </xs:element>
          <xs:element name="getSupportedUnitsResponse">
            <xs:complexType>
              <xs:sequence>
                <xs:element name="Response" type="s1:ArrayOfString" nillable="true"/>
              </xs:sequence>
            </xs:complexType>
          </xs:element>
        </xs:schema>
      </wsdl:types>
      <wsdl:message name="checkConnectionIn_doc">
        <wsdl:part name="parameters" element="ns0:checkConnection"/>
      </wsdl:message>
      <wsdl:message name="checkConnectionOut_doc">
        <wsdl:part name="parameters" element="ns0:checkConnectionResponse"/>
      </wsdl:message>
      <wsdl:message name="doMeasurementImportIn_doc">
        <wsdl:part name="parameters" element="ns0:doMeasurementImport"/>
      </wsdl:message>
      <wsdl:message name="doMeasurementImportOut_doc">
        <wsdl:part name="parameters" element="ns0:doMeasurementImportResponse"/>
      </wsdl:message>
      <wsdl:message name="doMeasurementsImportIn_doc">
        <wsdl:part name="parameters" element="ns0:doMeasurementsImport"/>
      </wsdl:message>
      <wsdl:message name="doMeasurementsImportOut_doc">
        <wsdl:part name="parameters" element="ns0:doMeasurementsImportResponse"/>
      </wsdl:message>
      <wsdl:message name="getErrorCodesIn_doc">
        <wsdl:part name="parameters" element="ns0:getErrorCodes"/>
      </wsdl:message>
      <wsdl:message name="getErrorCodesOut_doc">
        <wsdl:part name="parameters" element="ns0:getErrorCodesResponse"/>
      </wsdl:message>
      <wsdl:message name="getSupportedUnitsIn_doc">
        <wsdl:part name="parameters" element="ns0:getSupportedUnits"/>
      </wsdl:message>
      <wsdl:message name="getSupportedUnitsOut_doc">
        <wsdl:part name="parameters" element="ns0:getSupportedUnitsResponse"/>
      </wsdl:message>
      <wsdl:portType name="xEM_MeasurementImportVi_Document">
        <wsdl:operation name="checkConnection">
          <wsdl:input message="tns:checkConnectionIn_doc"/>
          <wsdl:output message="tns:checkConnectionOut_doc"/>
        </wsdl:operation>
        <wsdl:operation name="doMeasurementImport">
          <wsdl:input message="tns:doMeasurementImportIn_doc"/>
          <wsdl:output message="tns:doMeasurementImportOut_doc"/>
        </wsdl:operation>
        <wsdl:operation name="doMeasurementsImport">
          <wsdl:input message="tns:doMeasurementsImportIn_doc"/>
          <wsdl:output message="tns:doMeasurementsImportOut_doc"/>
        </wsdl:operation>
        <wsdl:operation name="getErrorCodes">
          <wsdl:input message="tns:getErrorCodesIn_doc"/>
          <wsdl:output message="tns:getErrorCodesOut_doc"/>
        </wsdl:operation>
        <wsdl:operation name="getSupportedUnits">
          <wsdl:input message="tns:getSupportedUnitsIn_doc"/>
          <wsdl:output message="tns:getSupportedUnitsOut_doc"/>
        </wsdl:operation>
      </wsdl:portType>
    </wsdl:definitions>
    Appreciate your quick response.
    Srini Sandaka

    Hi,
    I diagnose the problem, the problem with the name space length.
    Orginal NameSpace: <i>urn:xEM_MeasurementImportWsd/xEM_MeasurementImportVi/document</i>
    Modified NameSpace: <i>urn:xEM_MeasurementImportWsd/xEM_MeasurementImportVi/documen</i>
    The <b>External Definitions</b> is recognizing only 60 characters namespace. If the namespace exceed 60 characters it is not showing any messages in the messages tab.
    Will make any problem to call the WebService from XI since we are changing the original namespace in the WSDL and imported into XI.
    How can we overcome this problem, is it a limitation.
    Thanks
    Srini Sandaka

  • Import SAP WSDL into External Definition

    Hi Friends,
    I'd like to import a WSDL into XI External Definition. However, the WSDL is gained from Web AS Web Service Navigator. So it is a zip file and consists of three WSDL files. How can I import them into the external definition?
    Thanks + Regards
    Jerome

    Hi Jerome,
    If you have three wsld files then aren't those three messages?
    have you tried importing them as external definitions one by one?
    you can check how the message structre looks like
    when you try to use the external definition inside a
    message mapping (remember you don't create message type from external definitions)
    Futher reference:
    http://help.sap.com/saphelp_nw04/helpdata/en/26/9e97b0f525d743882936c2d6f375c7/content.htm
    BTW
    while creating external defnitions (WSDL)
    you can only choose wsld file or XML - nothing else
    Regards,
    michal

  • Problem Loading WSDL in External Definition

    Hello people,
    i'm having some problems When i'm Importing the WSDL in external definitions, the Messages are not being Recognized, it doesnt load the message structures, if i try in any other program that uses the WSDL like SoapUI, the wsdl works fine.
    Here is the WSDL links
    http://siatepqa.suseso.cl:8888/Siatep/WSToken?wsdl
    http://siatepqa.suseso.cl:8888/Siatep/WSIngreso?wsdl
    http://siatep.suseso.cl:8888/SusesoSiatep/WSToken?wsdl
    http://siatep.suseso.cl:8888/SusesoSiatep/WSIngreso?wsdl
    anyone can help?

    Hi,
    http://siatepqa.suseso.cl:8888/Siatep/WSToken?wsdl
    I checked the WSDL from the above link. The issue that I noticed is that you are importing the schema structure in your above WSDL. PI is unable to recognize the external reference. SOAPUI (or similar tool) will recognize the external reference.
    Best option is that you should re-modify your above WSDL and provide the schema in this WSDL itself. It should then work just fine.
    Hope this helps.
    Regards,
    Neetesh

  • Import external definition to message type

    Hello
    I have scenario file to IDOC.
    I don’t know way in this time I not successful to import my external definition to message type.
    Any idea?
    Elad

    Hello again,
    I try to solve mapping problem
    Hello again,
    I have scenario from file(xml) to IDOC.
    In outbound side I have XSD file and I imported this file and I use with him in outbound interface.
    In inbound side I have IDOC.
    I have mapping problem issue.
    When I test this mapping I have this error message:
    Cannot produce target element /ZORD_CREATE. Check xml instance is valid for source XSD and target-field mapping fulfills requirements of target XSD
    Any idea?
    Elad

  • Issue while importing the WSDL file in the External Definitions - PI 7.0

    Dear all Experts
    After importing the WSDL file in the external External Definitions we are not able to view the " name and namespace " in the messages tab.
    Request you to advise on the issue.
    We are using the PI 7.0
    Regards
    Machindra Patade

    Dear All
    Got the answer"
    The problem is in the namespace description LENGTH,
    Note the following restrictions for XI or PI installations:
    ·         Maximum length of repository namespaces and XML namespaces: 60 Characters. Due to this restriction, the import of XSD files and WSDL files prepares difficulties as an external definition; you can solve these difficulties using Note 901988.
    ·         Maximum length of object names in the Integration Repository and Integration Directory: 120 characters
    As of SAP NetWeaver Process Integration 7.10 Support Package 7, the enhancement of the maximum length of namespaces to 255 is supported in the configuration and runtime.
    Please check the below SAP 2 notes in regards to above mail.
    SAP Note 901988 - Integration Builder: Namespace of external definitions
    SAP Note 870809 - Integration Builder: Length of namespaces and object names

  • "Messages" problem after importing .xsd file as external definition

    Hello,
    I received an .xsd file from a customer and need to import it as an "External Definition" in order to create the "Message Interface". The structure of the xsd looks like this:
    <?xml version="1.0" encoding="ISO-8859-1"?>
    <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:px="http://www.opentrans.org/XMLSchema/1.0" targetNamespace="http://www.opentrans.org/XMLSchema/1.0" elementFormDefault="qualified">
    <xsd:element name="ORDER">
    </xsd:element>
    <xsd:element name="ADDRESS">
    </xsd:element>
    <xsd:element name="ARTICLE_ID">
    </xsd:element>
    </xsd:schema>
    After importing and looking at the tab "Messages" I get numerous entries, for each <xsd:element> I get one message! But I basically only need one "Message" that holds my complete xsd-file.
    I tried inserting <xsd:element name="COMPLETEORDER"> right after the <xsd:schema>-Tag but that didn't work either. Somehow I need to sum up all the <xsd:elements>.
    Does anyone have an idea? Thank you very much!
    Peter

    Hello Prateek, Hello everyone,
    I now know what the problem is. I downloaded XMLspy and checked on the structure:
    <?xml version="1.0" encoding="ISO-8859-1"?>
    <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:px="http://www.opentrans.org/XMLSchema/1.0" targetNamespace="http://www.opentrans.org/XMLSchema/1.0" elementFormDefault="qualified">
    <xsd:element name="ORDER">
    </xsd:element>
    <xsd:element name="ADDRESS">
    </xsd:element>
    <xsd:element name="ARTICLE_ID">
    </xsd:element>
    <xsd:simpleType name="dtBOOLEAN">
    </xsd:simpleType>
    <xsd:simpleType name="dtCOUNTRIES">
    </xsd:simpleType>
    <xsd:element name="SUPPLIER_AID">
    </xsd:element>
    <xsd:simpleType name="typeSUPPLIER_AID">
    </xsd:simpleType>
    </xsd:schema>
    Between the long list of <xsd:element> tags there are some simpleTypes on the same
    level. Now if I insert
    <xsd:element name="COMPLETEORDER">
    <xsd:complexType>
    <xsd:sequence>
    on top, the <xsd:sequence> would be on the same level as the simpleTypes - which is not valid!
    But can I just move all the simpleTypes, e.g. into an <xsd:element>??
    That would be changing the customer's structure which I think is not a good thing!?
    Thank you again for your help! I really appreciate it!
    Best regards,
    Peter

Maybe you are looking for

  • Message Splitting with BPM

    Someone knows about an example on splitting a message into several messages (multiline element), the target message type is of one type.

  • Problem exposing Accessor Methods on View object (ViewRowImpl.java)

    JDeveloper 9.03 I have a view link, ViewLinkSourceDest, that links two view objects Source and Destination. Each view object has its respective ViewRowImpl.java file created. I have selected "Generate Accessor in View Object" in View link Properties

  • Sending Meeting Requests through BPEL

    Hi, I am working on Jdeveloper 11.1.1.5.0, I want to send a meeting request(to multiple recipients) on Outlook or any other mail account through BPEL. Can anyone suggest how to go about that?

  • 9/23 Updater Summary

    Folks, Since the bugs fixed in the updater are not listed by Apple, I'm posting my summary findings after using the update for the last week. 1) ITMS songs not playing: this problem seems to be fixed; there are scattered reports that some still exper

  • Lightroom 3.4.1 unable to open

    I am unable to open Lightroom after importing an image.  The heading now reads when I try to open it,  Lightroom-  Opening Catalogue: - Wrights Water Garden 10 Feb 2007 (88) jpg.Ircad  I guess I clicked on something I shouldn't have as I am new to th