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

Let’s learn the Web Service in SAP – XSD Schema Error in External Web Service URL. Commonly when we attempt to make Purchaser Intermediary for the outside Web Administration (URL), we get blunder while getting to the WSDL/Diagram. The mistake can be a direct result of firewall, believed network, URL confirmation or approval issues. In any case, when all the organization and approval issues are settled, on the off chance that you actually get blunder in WSDL/Pattern, it is profoundly conceivable that your Internet Administration URL has the connection to Construction Area which it can’t distinguish at runtime wizard while making the Purchaser Intermediary. XSD Schema Error in External Web Service URL.

Let’s assume you are attempting to make buyer intermediary in SE80 like displayed beneath.

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

Be that as it may, you are trapped in the step “Enter the URL for getting to the WSDL/Composition”.

Blunders can be like underneath: “500 Interior Server Mistake”.

Error can be like “500 SSL Peer Certificate Untrusted”.

Error in URL accessing the WSDL/Schema can also be for .XSD like below.

Sample xsd errors in WSDL URL:

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

“Document ContractService.xsd was not joined in light of the fact that it has an invalid record augmentation not permitted by the framework settings”

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

“… .xsd ” mistake

by the manner in which XSD implies XML Pattern Definition

More often than not, WSDL URL has the hyper interface (URL) to the pattern area. Rather than the definition , it has a URL connect to pattern place where we can see the genuine mapping definition and properties. In such Web Administrations, assuming 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. You can definitely relax, the neighborhood WSDL record would be dynamic and would work precisely like the WSDL URL. However, we really want to do a little change in the neighborhood WSDL record.

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

Underneath steps would exhibit in subtleties, how we can supplant the xsd mapping area with the specific xsd blueprint 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 record as .txt in your nearby machine. Screen capture of the txt record opened in wordpad underneath.

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

Investigate the either 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 succession 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 record with the xsd:schema from the schemaLocation.

PS: Do not copy the first line of the page source (as marked in image 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 neighborhood WSDL document. The xsd blueprint blunder ought to be settled.