Share via


Error while importing WSDL to APIM

Question

Thursday, February 20, 2020 12:13 PM

I am trying to import a WSDL in API Management using the  Import API functionality. I am selecting SOAP pass-though

So when trying to import I am getting following message:

Unable to create API from WSDL

Informational: ParsingXMLStarted : Started parsing XML

Informational: ParsingXMLComplete : Completed parsing XML

Verbose: WsdlImportRuleVerifyWadl11Schema : WSDL validated against XML Schema

Informational: WsdlPrecheckComplete : Completed WSDL verification. WSDL is considered valid.

Informational: WsdlParsingStarted : Service : Endpoint :

Informational: WsdlIdentification : WsdlVersion: 'Wsdl11' TargetNamespace: 'urn:Test.Application.V2'.

Informational: LoadedSchema : Target Namespace: 'urn:Test.Application.V2'.

Informational: LoadedSchemas : Loaded '1' schemas.

Informational: LoadedTypes : Loaded '3' types.

Informational: LoadedMessages : Loaded '3' messages.

Informational: LoadedInterfaces : Loaded '1' interfaces.

Informational: LoadedBindings : Loaded '1' bindings.

error that i am getting is;

One or more fields contain incorrect values:

  • Parsing error(s): Unable to parse WSDL

 Activity log shows same in Json format, but no directional info:

"status": {

        "value": "Failed",

        "localizedValue": "Failed"

    },

    "subStatus": {

        "value": "BadRequest",

        "localizedValue": "Bad Request (HTTP Status Code: 400)"

    },

    "submissionTimestamp": "2020-02-20T11:45:55.1424852Z",

    "subscriptionId": "6026d334-9ca9-46e8-911c-aa0b0b36ecfe",

    "tenantId": "229365ac-76e3-4cbb-b87e-729538eb5fb4",

    "properties": {

        "statusCode": "BadRequest",

        "serviceRequestId": "14232d72-6714-49c8-8d25-7a60e0538cf3",

"statusMessage": "{\error\:{\code\:\ValidationError\,\message\:\One or more fields contain incorrect values:\,\details\:[{\code\:\ValidationError\,\target\:\representation\,\message\:\Parsing error(s): Unable to parse WSDL\},{\code\:\ValidationError\,\target\:\representation\,\message\:\Parsing error(s): {\\events\\:[{\\level\\:\\Informational\\,\\event\\:\\ParsingXMLStarted\\,\\message\\:\\Started parsing XML\\},{\\level\\:\\Informational\\,\\event\\:\\ParsingXMLComplete\\,\\message\\:\\Completed parsing XML\\},{\\level\\:\\Verbose\\,\\event\\:\\WsdlImportRuleVerifyWadl11Schema\\,\\message\\:\\WSDL validated against XML Schema\\},{\\level\\:\\Informational\\,\\event\\:\\WsdlPrecheckComplete\\,\\message\\:\\Completed WSDL verification. WSDL is considered valid.\\},{\\level\\:\\Informational\\,\\event\\:\\WsdlParsingStarted\\,\\message\\:\\Service :  Endpoint : \\},{\\level\\:\\Informational\\,\\event\\:\\WsdlIdentification\\,\\message\\:\\WsdlVersion: 'Wsdl11' TargetNamespace: 'urn:Test.Application.V2'.\\},{\\level\\:\\Informational\\,\\event\\:\\LoadedSchema\\,\\message\\:\\Target Namespace: 'urn:Test.Application.V2'.\\},{\\level\\:\\Informational\\,\\event\\:\\LoadedSchemas\\,\\message\\:\\Loaded '1' schemas.\\},{\\level\\:\\Informational\\,\\event\\:\\LoadedTypes\\,\\message\\:\\Loaded '3' types.\\},{\\level\\:\\Informational\\,\\event\\:\\LoadedMessages\\,\\message\\:\\Loaded '3' messages.\\},{\\level\\:\\Informational\\,\\event\\:\\LoadedInterfaces\\,\\message\\:\\Loaded '1' interfaces.\\},{\\level\\:\\Informational\\,\\event\\:\\LoadedBindings\\,\\message\\:\\Loaded '1' bindings.\\}]}\}]}}"

    },

    "relatedEvents": []

All replies (5)

Thursday, February 20, 2020 12:16 PM

This can happen when your wsdl is referencing schemas with location that APIM can not discover.

1. You might need to make it a complete wsdl by hand so that its not referencing anything thats unreachable.

2. Or upload the imported schamas to a blob storage and then you can edit the wsdl to point to this location.

Pi_xel_xar

Blog: My Blog

BizTalkApplicationDeploymentTool: BizTalk Application Deployment Tool/


Thursday, February 20, 2020 3:33 PM

Thanks for prompt response.

I removed all schema definition dependencies earlier that were in include file section. There are few more schema that is being referred from places like http://schemas.xmlsoap.org, http://docs.oasis-open.org, http://www.w3.org and few 2 XSDs from government portals.

Do you suggest to remove these as well. Also this WSDL files  is validated clean using SOAP UI. 
Is there any other way to validate it for API manager to get clear error response, any suggestion in this direction would be helpful.


Friday, February 21, 2020 6:31 AM

no those would be ok,

but when u say u removed all others, then this would make wsdl incomplete because if u just removed the references but the wsdl itself has elements/ records/type definitions from those then it would not work.

is it a local wsdl ? may be locally on soapui ur schema references are getting resolved.

Pi_xel_xar

Blog: My Blog

BizTalkApplicationDeploymentTool: BizTalk Application Deployment Tool/


Friday, February 21, 2020 10:45 AM

i should have used resolved (rather removed) all references. Yes it was a local WSDL, before i tied to resolve xsd dependencies. When  this resultant WSDL (placed in independent folder without any XSD this time) is being loaded in SOAP UI, no errors there. 


Friday, February 21, 2020 2:53 PM

can u share the wsdl?

Pi_xel_xar

Blog: My Blog

BizTalkApplicationDeploymentTool: BizTalk Application Deployment Tool/