Uploading WSDL as File
A common problem in SOAP services is that even though the WSDL is accessible via an https address, the XSD files inside it remain accessible via an http address, which causes file resolution problems.If the method of defining the service to Apinizer with the WSDL file upload option is selected, there are points to be noted that differ from other upload options.
Identifying and Downloading XSD Files
Identifying and Downloading XSD Files
Due to WSDL structure, it can reference different XSD files, and these references also need to be uploaded to the system.Updating WSDL alone may not be sufficient, if there are places in XSD that reference another XSD, these must also be updated.Visual showing the updating of locations within WSDL is shown below:
1
Find XSD Files
It is necessary to find which XSD files need to be uploaded together with the WSDL.
2
Download XSD Files
The contents of these XSD files need to be downloaded as files.
3
Update WSDL
After the files are downloaded, each one’s location within the WSDL must be updated.Updating WSDL alone may not be sufficient, if there are places in XSD that reference another XSD, these must also be updated.

Preparing Files as ZIP
Preparing Files as ZIP
For XSD files shown as references to be uploaded to the system together with the WSDL, Apinizer requires the files to be “zipped” together.Example visual showing file directory paths is shown below:
The visual of these files in zipped form is as follows:


Multiple Ports in SOAP Service
SOAP services can have multiple ports as shown in the following visual.
In this case, Apinizer uses the first of these ports.
1
Edit WSDL
Create a separate WSDL file for each port. Edit the WSDL so that only the relevant port remains in it.
2
Upload WSDL
Upload the edited WSDL file to Apinizer.
3
Create API Proxy
Create a separate API Proxy for each port.

