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

Similar Messages

Importing WSDL into External Definitions

Hi,
I got WSDLs from WAS WS Navigator, I have imported the WSDL from porttypes 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"?>
<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: urn:xEM_MeasurementImportWsd/xEM_MeasurementImportVi/document
Modified NameSpace: urn:xEM_MeasurementImportWsd/xEM_MeasurementImportVi/documen
The External Definitions 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

No messages under the 'Messages' tab for imported WSDL in External Definitions

Dear All,
I import this WSDL to the External Definitions but it is not showing any messages in the 'Messages' tab while WSDL clearly has message interfaces in it. Attached is the WSDL. You help is very much appreciated.
Regards,
Adil Khalil

Hi, imported wsdl shouldn't have any import instruction.
All import instruction should be changed to content of importing file.
I see the code <xsd:import namespace="http://ouaf.oracle.com/"/> in your file.
Hmm. but I imported you file and everything is fine
Message was edited by: Mikhail Koshkin

Loading WSDL to the XI

hello experts
I have XI7.0 and a scenario RFC2WS. I am trying to load the WSDL to the XI and when I enter it to the MESSAGE INTERFACE I dont see any of the methods that the WSDL has.
in XML SPY I am able to make a SOAP REQUEST out of the WSDL.
I try to play with the schema (make one schema) or with the name spaces but with out any success.
the wsdl is:
<?xml version="1.0" encoding="UTF-8"?>
<wsdl:definitions xmlns:apachesoap="http://xml.apache.org/xml-soap" xmlns:impl="http://compulsoryRenewService.services.elementar.migdal.co.il" xmlns:intf="http://compulsoryRenewService.services.elementar.migdal.co.il" xmlns:tns1="http://vo.compulsoryRenewService.services.elementar.migdal.co.il" xmlns:tns2="http://common.services.elementar.migdal.co.il" xmlns:tns3="http://exceptions.common.fw.ness.com" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" targetNamespace="http://compulsoryRenewService.services.elementar.migdal.co.il">
 <wsdl:types>
 <schema elementFormDefault="qualified" targetNamespace="http://compulsoryRenewService.services.elementar.migdal.co.il" xmlns="http://www.w3.org/2001/XMLSchema">
 <import namespace="http://vo.compulsoryRenewService.services.elementar.migdal.co.il"/>
 <import namespace="http://common.services.elementar.migdal.co.il"/>
 <import namespace="http://exceptions.common.fw.ness.com"/>
 <element name="getCompulsoryRenewData">
 <complexType>
 <sequence>
 <element name="anaf" type="xsd:int"/>
 <element name="year" type="xsd:string"/>
 <element name="month" type="xsd:string"/>
 </sequence>
 </complexType>
 </element>
 <element name="getCompulsoryRenewDataResponse">
 <complexType>
 <sequence>
 <element name="getCompulsoryRenewDataReturn" type="tns1:PolicyRenewDataList"/>
 </sequence>
 </complexType>
 </element>
 <complexType name="ArrayOf_tns1_PolicyRenewData">
 <sequence>
 <element maxOccurs="unbounded" minOccurs="0" name="item" type="tns1:PolicyRenewData"/>
 </sequence>
 </complexType>
 <element name="fault" type="tns3:FatalException"/>
 </schema>
 <schema elementFormDefault="qualified" targetNamespace="http://common.services.elementar.migdal.co.il" xmlns="http://www.w3.org/2001/XMLSchema">
 <import namespace="http://compulsoryRenewService.services.elementar.migdal.co.il"/>
 <import namespace="http://vo.compulsoryRenewService.services.elementar.migdal.co.il"/>
 <import namespace="http://exceptions.common.fw.ness.com"/>
 <complexType name="BaseResult">
 <sequence>
 <element name="errorMessage" nillable="true" type="xsd:string"/>
 <element name="errorCode" type="xsd:int"/>
 </sequence>
 </complexType>
 </schema>
 <schema elementFormDefault="qualified" targetNamespace="http://vo.compulsoryRenewService.services.elementar.migdal.co.il" xmlns="http://www.w3.org/2001/XMLSchema">
 <import namespace="http://compulsoryRenewService.services.elementar.migdal.co.il"/>
 <import namespace="http://common.services.elementar.migdal.co.il"/>
 <import namespace="http://exceptions.common.fw.ness.com"/>
 <complexType name="PolicyRenewData">
 <sequence>
 <element name="policyId" nillable="true" type="xsd:decimal"/>
 <element name="id" nillable="true" type="xsd:decimal"/>
 <element name="endDate" nillable="true" type="xsd:string"/>
 <element name="anaf" nillable="true" type="xsd:decimal"/>
 <element name="startDate" nillable="true" type="xsd:string"/>
 <element name="runninigNum" nillable="true" type="xsd:decimal"/>
 </sequence>
 </complexType>
 <complexType name="PolicyRenewDataList">
 <complexContent>
 <extension base="tns2:BaseResult">
 <sequence>
 <element name="policyRenewDataList" nillable="true" type="impl:ArrayOf_tns1_PolicyRenewData"/>
 </sequence>
 </extension>
 </complexContent>
 </complexType>
 </schema>
 <schema elementFormDefault="qualified" targetNamespace="http://exceptions.common.fw.ness.com" xmlns="http://www.w3.org/2001/XMLSchema">
 <import namespace="http://compulsoryRenewService.services.elementar.migdal.co.il"/>
 <import namespace="http://vo.compulsoryRenewService.services.elementar.migdal.co.il"/>
 <import namespace="http://common.services.elementar.migdal.co.il"/>
 <complexType name="GeneralException">
 <sequence/>
 </complexType>
 <complexType name="FatalException">
 <complexContent>
 <extension base="tns3:GeneralException">
 <sequence/>
 </extension>
 </complexContent>
 </complexType>
 </schema>
 </wsdl:types>
 <wsdl:message name="FatalException">
 <wsdl:part name="fault" element="intf:fault"/>
 </wsdl:message>
 <wsdl:message name="getCompulsoryRenewDataResponse">
 <wsdl:part name="parameters" element="intf:getCompulsoryRenewDataResponse"/>
 </wsdl:message>
 <wsdl:message name="getCompulsoryRenewDataRequest">
 <wsdl:part name="parameters" element="intf:getCompulsoryRenewData"/>
 </wsdl:message>
 <wsdl:portType name="CompulsoryRenewService">
 <wsdl:operation name="getCompulsoryRenewData">
 <wsdl:input name="getCompulsoryRenewDataRequest" message="impl:getCompulsoryRenewDataRequest"/>
 <wsdl:output name="getCompulsoryRenewDataResponse" message="impl:getCompulsoryRenewDataResponse"/>
 <wsdl:fault name="FatalException" message="impl:FatalException"/>
 </wsdl:operation>
 </wsdl:portType>
 <wsdl:binding name="CompulsoryRenewServiceSoapBinding" type="intf:CompulsoryRenewService">
 <wsdlsoap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
 <wsdl:operation name="getCompulsoryRenewData">
 <wsdlsoap:operation soapAction=""/>
 <wsdl:input name="getCompulsoryRenewDataRequest">
 <wsdlsoap:body use="literal"/>
 </wsdl:input>
 <wsdl:output name="getCompulsoryRenewDataResponse">
 <wsdlsoap:body use="literal"/>
 </wsdl:output>
 <wsdl:fault name="FatalException">
 <wsdlsoap:fault name="FatalException" use="literal"/>
 </wsdl:fault>
 </wsdl:operation>
 </wsdl:binding>
 <wsdl:service name="CompulsoryRenewServiceService">
 <wsdl:port name="CompulsoryRenewService" binding="intf:CompulsoryRenewServiceSoapBinding">
 <wsdlsoap:address location="http://mguxp70:9064/ElementarSOA/services/CompulsoryRenewService"/>
 </wsdl:port>
 </wsdl:service>
</wsdl:definitions>
if any one know what is missing, or to add something to the WSDL in order to load it and see the method will be much of an help.
Thank you very much for your help
Kfir

Hi Kfir,
I was able to load your wsdl file and can see three messages (FatalException,getCompulsaryRenewDateRequest, getCompulsaryRenewDateResponse)
I will suggest you to do like this:
1. Open your wsdl in a notepad
2. Find for namespace http://compulsoryRenewService.services.elementar.migdal.co.il (namespace length = 61 characters)
3. Replace with http://compulsoryRenewService.services.elementar.migdal.co (new length = 8 character)
4. Save and try to import as a wsdl in external definitions. Keep option of Messages as "From all Available Message Definitions"
Regards
Suraj

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

WSDL With External References

Hello,
I need to import a wsdl in external definition ,that has 2 xsds as external references.
But when I import the wsdl,I am not able to find the wsdl pointing to the two xsds .
Can anyone help me with the this?
Thanks in advance.
Regards,
Sriparna

Hello,
The xsds will stay as is. What you can do is:
1.) Open the WSDL ED
2.) Go to the External References Tab
3.) You will see a source and a name column
4.) Click on the name(column) of any xsd that you want to be referenced
5.) Press ctrl+c
6.) Open the XSD ED
7.) Click the edit button
8.) Under the Source field, press ctrl+v
9.) Save and activate
Hope this helps,
Mark

Need of External definition

Hey guys
i was just wondering as to why we need to import an XSD or WSDL in External definition when we can directly import that using the tabs in Datatypes and Message Interface.
is it because of shipment purposes?do we always need to create an External definition first and then import that in datatype or Message Interface?
thanx
ahmad

Hi Ahmad,
      Added to Archanas point,External Defination are used in XI to import the any wsdl files from any remote stystem or any landscape.
    Let's take an example you have webservice which is not in your landscape and you want to use that webservice in your business requirement...in such a situation you can imort that wsdl file as external defeniation in XI and you can map the reqired fields....here we are making use of webservice as external definiation which is not in ur landscape.
    Hope you clear about what is the use of exeternal definition
Thanks and Regards,
chandu.

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

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.

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?

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

Loading external definition

I've loaded external definition which has encoding UTF-8 but when i loaded the XSD it shows that its ISO-8859-1. Why is it changing the encoding?
Thanks,
Kalpana

I dont think so. Please let us know if you observe any issues during the testing.
But it shouldnt cause problems mostly.

"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

External definitions problem

hi experts, i have wsdl file, i upload it to xi as external definition but there are no any messages in "messages" tab.
i tried to generate some requests using Altova xm spy so it works fine, in XI it is not.
Help pls.

Hi,
Are you able to deploy the External definition without any issues?
If you have deployed it, then go to the WSDL tab in the external definition and check.
If you are able to successfully deploy it, then create Message interface and check the Context objects, you would be able to see the structure.
If you are not able to see the messages then there should be some issue with the WSDL.
Thanks,

Problem Loading WSDL in External Definition

Similar Messages

Maybe you are looking for