Web Service in SAP – Part IV – XSD Schema Error in External Web Service URL

Ordinarily, when we attempt to create a Consumer Proxy for the external web service (URL), we encounter an error while accessing the WSDL/XSD schema. This error could be due to firewall issues, network trust, URL authentication, or authorization problems. However, once all network and authorization issues are resolved, if you still encounter errors in the WSDL/XSD schema, it is highly likely that your web service in SAP – Part IV – XSD Schema Error in External Web Service URL has a reference to the schema location that cannot be resolved at runtime during the creation of the Consumer Proxy.

Let’s assume you are attempting to create a consumer proxy in SE80, as shown below. During this process, you might encounter an XSD Schema Error in External Web Service URL, which typically occurs when the schema definitions in the web service are not compatible with the expected structure in SAP.

You give the name and continue with the Undertaking Administrations Make Wizard.

However, you are caught in the step “Enter the URL for getting to the WSDL/Diagram“.

Blunders can be like underneath: “500 Inward Server Mistake“.

Blunder can be like “500 SSL Companion Endorsement Untrusted“.

Mistake in URL getting to the WSDL/Blueprint can likewise be for .XSD like underneath.

Sample xsd errors in WSDL URL:

“Blunder while transferring the xsd file(schema) in web administrations definition”

“Record ContractService.xsd was not appended on the grounds that it has an invalid document expansion not permitted by the framework settings”

“Special case happened in correspondence structure: Blunder in HTTP Framework:500Internal Server Mistake”

“… .xsd ” blunder

by the manner in which XSD implies XML Composition Definition

More often than not, WSDL URL has the hyper connect (URL) to the composition area. Rather than the definition , it has a URL connect to diagram place where we can see the genuine pattern definition and properties. In such Web Administrations, on the off chance that we attempt to consume the WSDL URL, we get mistake. To stay away from that blunder, we really want to utilize the WSDL neighborhood record. Relax, the neighborhood WSDL record would be dynamic and would work precisely like the WSDL URL. Be that as it may, we want to do a little change in the nearby WSDL record.

We want to supplant the connection to outline area with the specific blueprint definition from the construction area URL in the WSDL neighborhood document. When we have the total composition definition supplanted in the WSDL, we ought to have the option to make the customer intermediary utilizing the neighborhood WSDL record.

Underneath steps would show in subtleties, how we can supplant the xsd blueprint area with the specific xsd composition definition. We have taken the public dnb tool compartment web administration for our model.

Step 1 – Refer to below link for dnb WSDL

We are referring to GDP_V4.wsdl.

Step 2 – Open the Web Service

Step 3 – Save the Web Service as .txt file

Save the WSDL document as .txt in your neighborhood machine. Screen capture of the txt document opened in wordpad beneath.

Step 4 – Look for <xsd:schema> Key Word

Investigate the either <xsd:schema> in the txt record (screen capture above) or on WSDL in program (screen capture beneath).

<xsd:schema> </xsd:schema>

Step 5 – Expand <xsd:schema> </xsd:schema>

<xsd:schema><xsd:import namespace=”http://www.dnb.com/DNB_WebServices/Providers/OrderAndInvestigations/GDP_V4/wsp_GDP_V4” schemaLocation=”https://toolkit-wsdl.dnb.com/ws/DNB_WebServices.Providers.OrderAndInvestigations.GDP_V4:wsp_GDP_V4?WSDL&fingerprint=P6DCJGGOL7NVDOIVFGQWX7EKOTZNG45M.xsd” /></xsd:schema>

Step 6 – Look for schemaLoation Key Word and schemaLocation Path

For this WSDL the schemaLocation way is:

Step 7 – Replace the xsd:schema in the WSDL file with the exact definition from the schemaLocation.

Open the schemaLocation Way URL in one more Tab in the program. It will give the full Sort meaning of the xsd:schema.

Remember to extend all before you duplicate the full definition.

Whenever it is extended, it is not any more yellow.

The simple method for extending all the grouping is by going to page source. Right snap on any area and go to View page source

Step 8 – Copy XSD Schema Definition and Replace

Duplicate the full xsd:schema and supplant in the first WSDL.txt document with the xsd:schema from the schemaLocation.

PS: Don’t duplicate the primary line of the page source (as set apart in picture above).

Tips: <xsd:schema> </xsd:schema> should be between <wsdl:types> </wsdl:types>.

Step 9 – Save the Web Service file with .WSDL extension

Step 10 – Choose the WSDL Source as Local File in the Wizard

Presently, any place you were attempting to utilize the WSDL URL, supplant it with your nearby WSDL record. The xsd outline blunder ought to be settled.