WSDL - Please validate your xml Schema...

system · February 6, 2015, 1:54pm

Hi All,

After several years i’m returning to SAP BODS exploring Webservices as a datasource.

After defining a datasource i can see in the external metadata the functions i want to use.

When i import one of these functions i get an error msg stating:

An Error occured while importing metadata: BODI 1111469) Error parsing the <> included in the xml… .
Error importing XML SChema from file.
…
Please validate your XML Schema using external schema validators.

Anybody any idea?

We are running an old BODS installation. (12.2.2.2)

I have attached a screenshot of the error + the mentioned XSD, but it includes others i think.

As datasource type i’m using web service.

Also, i’m using this WSDL also in BI4 Reporting. I have a .unx universe that returns data with the same URL. So i’m guessing there is an issue on BODS side?

Thanks !
Laurens
wsdl.zip (99.0 KB)

lverstraeten (BOB member since 2006-11-02)

system · February 9, 2015, 10:39am

Hi,

Nobody any idea?

Manoj_d, Werner Daehn you guys have helped me quite a lot in the past , can you shed some light?

Kind regards
Laurens

lverstraeten (BOB member since 2006-11-02)

system · February 9, 2015, 3:52pm

looks like the parser is not able to resolve the namespace references for element if it’s declared in following way

<xs:complexType name=“StatusMessage”>
-xs:sequence
<xs:element name=“Description” type=“xs:string” nillable=“true” minOccurs=“0”/>
<xs:element name=“QueryTime” type=“xs:double” minOccurs=“0”/>
<xs:element name=“Status” type=“q1:ResponseStatus” minOccurs=“0” xmlns:q1=“http://schemas.datacontract.org/2004/07/De.Matrikon.Amcpmws.Data”/>

you will have to save the WSDL and all dependent XSDs to disk and edit the files to move the schema declaration to top and of schema definition

in this case, remove the xmlns:q1=“http://schemas.datacontract.org/2004/07/De.Matrikon.Amcpmws.Data” from the element declaration and move it the schema tag add it along with the other xmlns declaration

do this for all such references and use this WSDL file see if that works

manoj_d (BOB member since 2009-01-02)

system · February 10, 2015, 12:40pm

Hi Manoj_d,

Thanks for the reply.

As i’m not an expert in this matter i find it difficult to understand what you mean.

As far as i can see, the namespaces are already defined in the first schema part.

If we look at a small part of the xsd file we see for element GetReport that he is referencing the same namespaces as the ones i have defined above?

Sorry if i’m not able to follow what you mean… .

<?xml version="1.0" encoding="UTF-8"?>

<xs:schema xmlns:xs=“http://www.w3.org/2001/XMLSchema” xmlns:msc=“http://schemas.microsoft.com/ws/2005/12/wsdl/contract” xmlns:soap=“http://schemas.xmlsoap.org/wsdl/soap/” xmlns:soap12=“http://schemas.xmlsoap.org/wsdl/soap12/” xmlns:soapenc=“http://schemas.xmlsoap.org/soap/encoding/” xmlns:tns=“http://tempuri.org/” xmlns:wsa=“http://schemas.xmlsoap.org/ws/2004/08/addressing” xmlns:wsa10=“http://www.w3.org/2005/08/addressing” xmlns:wsam=“http://www.w3.org/2007/05/addressing/metadata” xmlns:wsap=“http://schemas.xmlsoap.org/ws/2004/08/addressing/policy” xmlns:wsaw=“http://www.w3.org/2006/05/addressing/wsdl” xmlns:wsdl=“http://schemas.xmlsoap.org/wsdl/” xmlns:wsp=“http://schemas.xmlsoap.org/ws/2004/09/policy” xmlns:wsu=“http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd” xmlns:wsx=“http://schemas.xmlsoap.org/ws/2004/09/mex” xmlns:xsd=“http://www.w3.org/2001/XMLSchema” elementFormDefault=“qualified” targetNamespace=“http://tempuri.org/”>
<xs:import namespace=“http://schemas.datacontract.org/2004/07/AmCpmPost” schemaLocation=“C:\app\Business Objects\SAP Data Services\ext\webservice\ProxyGetReportIProxy_GetReport_InputMessage6.xsd”></xs:import>
<xs:import namespace=“http://schemas.datacontract.org/2004/07/De.Matrikon.Amcpmws.Data” schemaLocation=“C:\app\Business Objects\SAP Data Services\ext\webservice\ProxyGetReportIProxy_GetReport_InputMessage4.xsd”></xs:import>
<xs:import namespace=“http://schemas.microsoft.com/2003/10/Serialization/Arrays” schemaLocation=“C:\app\Business Objects\SAP Data Services\ext\webservice\ProxyGetReportIProxy_GetReport_InputMessage0.xsd”></xs:import>
<xs:element name=“GetRawOperatorInterventionsRelativeDatesForPath”>
xs:complexType
xs:sequence
<xs:element minOccurs=“0” name=“userName” nillable=“true” type=“xs:string”></xs:element>
<xs:element minOccurs=“0” name=“referenceStartDate” nillable=“true” type=“xs:string”></xs:element>
<xs:element minOccurs=“0” name=“referenceEndDate” nillable=“true” type=“xs:string”></xs:element>
<xs:element minOccurs=“0” name=“top” type=“xs:int”></xs:element>
<xs:element minOccurs=“0” name=“path” nillable=“true” type=“xs:string”></xs:element>
<xs:element minOccurs=“0” name=“plant” nillable=“true” type=“xs:string”></xs:element>
<xs:element minOccurs=“0” name=“bu” nillable=“true” type=“xs:string”></xs:element>
<xs:element minOccurs=“0” name=“site” nillable=“true” type=“xs:string”></xs:element>
<xs:element minOccurs=“0” name=“sort” nillable=“true” type=“xs:string”></xs:element>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name=“GetRawOperatorInterventionsRelativeDatesForPathResponse”>
xs:complexType
xs:sequence
<xs:element xmlns:q1=“http://schemas.datacontract.org/2004/07/AmCpmPost” minOccurs=“0” name=“GetRawOperatorInterventionsRelativeDatesForPathResult” nillable=“true” type=“q1:RawOperatorInterventionsResponse”></xs:element>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name=“GetReport”>
xs:complexType
xs:sequence
<xs:element minOccurs=“0” name=“reportName” nillable=“true” type=“xs:string”></xs:element>
<xs:element minOccurs=“0” name=“userName” nillable=“true” type=“xs:string”></xs:element>
<xs:element xmlns:q2=“http://schemas.datacontract.org/2004/07/AmCpmPost” minOccurs=“0” name=“queryParams” nillable=“true” type=“q2:QueryParameters”></xs:element>
<xs:element xmlns:q3=“http://schemas.datacontract.org/2004/07/De.Matrikon.Amcpmws.Data” minOccurs=“0” name=“pathsArray” nillable=“true” type=“q3:ArrayOfPathFilter”></xs:element>
<xs:element minOccurs=“0” name=“returnDebugInfo” type=“xs:boolean”></xs:element>
<xs:element xmlns:q4=“http://schemas.datacontract.org/2004/07/De.Matrikon.Amcpmws.Data” minOccurs=“0” name=“args” nillable=“true” type=“q4:ArrayOfArg”></xs:element>
</xs:sequence>
</xs:complexType>
</xs:element>

lverstraeten (BOB member since 2006-11-02)

system · February 12, 2015, 9:56am

Hi,

As it’s working in BI4 Information Design tool is still have the feeling the issue is at BODS side and not the structure.

We have other applications using this WSDL as a source as well.

Would upgrading to BODS 4.2 provide a solution?

Kind regards
Laurens

lverstraeten (BOB member since 2006-11-02)

system · February 12, 2015, 3:57pm

no, upgrading to 4.2 will make no difference, can you send me the WSDL file along with the dependent XSds, let me take a look

email these files to mdhyani at hotmail

manoj_d (BOB member since 2009-01-02)

system · February 16, 2015, 10:19am

Hi,

I imported the WSDL in a higher version and it works fine.

I guess there is an issue with the old version?

Kind regards
Laurens

lverstraeten (BOB member since 2006-11-02)